Analysis and Design of the UniRec Gym System - Case Study Example

System Design Report Contents 3 Economic Feasibility 4 Net Present Value (NPV) 4 Return on Investment (ROI) 5 Pay BackAnalysis (PBA) 5 Physical Design 5 Physical DFD for Level 1 diagrams 6 Physical Data Stores 7 Data Store methods 8 Processes for Implementation 8 Automated Processes 9 Manual Processes 9 Interface Design 9 Interface Structure Chart 9 Interface Template 10 Storyboard 11 Error handling information 12 Data attributes for the database tables 14 Button Functions 15 Report for interface designed 16 Program Design 16 Structure Chart 17 Program Source code 18 Program Specification 19 References 21 Abstract The report focuses on the analysis and design of the UniRec Gym System and all the factors that ought to be considered in all the processes entailed in the execution and implementation of the system. The report structure will follow a specific approach in highlighting the key areas of the system design specification. These essential components that are to be looked into are outlines and further explained below in the report content readings. Economic Feasibility When looking into the economic feasibility study of the proposed system one has to first develop and outline the cost benefit analysis of implementing this system. The additional advantage of conducting the economic feasibility study is that it aids in developing a preliminary projecting of the new client server based system’s benefits in terms of the monetary returns or revenues expected from using the system. The benefits of the new system are expected to mainly come from various sources, that is, one of them being from the increased sales from the rental of the DVDs via the online platform system. The costs incurred in developing the system also form an important part of calculating and determining the economic feasibility of the system. The costs include the costs for acquiring the hardware and software components used during development. Another expense that would be incurred entails the maintenance costs that are factored in during the running processes of the daily operation costs, for example, renting server and hosting space online. The Time Value of Money provides the concept of money being more valuable tomorrow than it is today. The time value of money is categorized into various components that mainly consist of: Net Present Value (NPV) This is determined via utilizing the discount rate which aids in defining the present value of the cash receipts and outlays. The Net Present Value (NPV) for this particular proposed system design and implementation project gives a -$27,998.06 amount. This simply means that the business has not yet realized any profit since it is still in the initial stages of its operation. Return on Investment (ROI) The Return on Investment (ROI) represents the ratio of the cash receipts to that of cash outlay. The Return on Investment (ROI) for this project is at 0.239% which means that the project has realized some resource yielding benefits. It represents the efficiency of the business by highlighting the common profitability of running this business project. Pay Back Analysis (PBA) The Pay Back Analysis (PBA) focuses on the periods expected for the breakeven point of the business project to be realized. It represents the amount of time necessary for the cumulative cash flow to be equivalent to the original and preliminary ongoing investment. The payback period (Breakeven Point) for the proposed system for the business project is expected to be within the 4th year of its operation. Physical Design The Physical Design of the system is represented via the various diagrams that outline the sketch data flow diagrams that highlight on the process entailed in operating the system. The main entities involved in this project’s operation involve the clients and staff that will manage the system. They will be recognized via the assigned IDs that identify them within the system. Implementing the physical design is mainly determined via the interactions and relations between the diverse data elements used in employing the project. An appropriate method of building an effective physical design is via superimposing a logical assembly on the provided data in relation to the established relationships. The data flow diagrams below showcase the various instances of the physical design. Physical DFD for Level 1 diagrams The data or information to be kept in the system database must be resolved via a cooperative system designer who is has the expertise to implement and execute the technological system database. The diagram below represents the Physical DFD for Level 1 diagram for the proposed technological system. This particular diagram explains and highlights on the processes involved in assigning the prospected clients membership IDs for use on the web based system. The physical configuration of the system is portrayed in the relationship diagrams shown below with the processes conducted within the system. The second diagram signifies the system processes conducted by a client renting for the DVDs online. Physical Data Stores The physical data stores mainly offer the space requirements for the storage of data and information regarding the company. These may include the customer and staff login in information for the system. The physical data stores would be mainly provide by the hosting servers which normally offer a lot of storage space for prospected future data. A database management system is implemented to help in the future storage and retrieval of the system information. Data Store methods The data storage methods are supposed to offer actualized data collection via techniques that aid in the storage and retrieval of the information through essential database management tools. These tools are expected to provide insights in the long run regarding customer behavior or desires towards using the system. The databases components offer an interface for managing the entities that utilize the system which in turn aids the administration in better understanding the business processes. The database table names utilized in this case entails the table utilized for storing information regarding the membership attributes for the clients that will acquire involvement in the system. The other one will be that for storage and inventory management of the products or service offered by the web based system, that’s, mainly the DVDs being put up for rentals. The tables involve: Membership/Clients table – holds information regarding the clients who have enrolled and are using the system based services. Staff_table – holds information regarding the staff or personnel that monitor the system and run the automated membership registration. They have elevated privileges within the web system. DVDs Inventory_table – Holds details of the DVDs being offered on rental. Processes for Implementation The process of implementing the system mainly entails the construction of all the level 1 diagrams which exemplify the interface programs and how their application on the system offer the appropriate attributes expected by the end users of the system. The implementation techniques are mainly divided into the modules that represent the processes that run the overall operation of the system. The processes are stated and outlined below: Automated Processes These processes represent the procedures entailed in implementing the computerized or programmed features of the proposed web based application. These include, for example issuance of receipts, which is automatically generated by the computer system. Manual Processes The manual process represents the stages within the system operation that have to be performed manually to enable an efficient and fluent execution of processes within the system. These processes are mainly performed by either the staff or the client and require their action to facilitate the execution of instructions within the system. They include membership activation by staff, or maybe authorization of a payment made via the system in the payment module process. These instances are represented in the DFD diagrams above. Interface Design The interface design is supposed to offer a prototype platform that represents the graphical representation of the system. It entails the links and connection between the different modules and components within the interface of the website. This signified via the structure of the overall system. Interface Structure Chart The interface structure and the template utilized as a system design prototype of the expected web system are represented in the pictures charts previewed below: Interface Template Storyboard This section represents the graphical outline that explains and interprets how the web system links are interconnected and the expected outcome form an executed instruction. For example clicking on a particular button would results in a particular action or pops out another interface for further action. The snapshot is shown below. Designs for the Interfaces In this section, the design of the interface represented is that of the rental processing. The interface below signifies all the features involved in the rental process for a particular client, Sue. Error handling information Error handling of the web system information is achieved assigning data abstraction attributes that protects vital information that might be tamper with was authorized access to those who are not privileged. The sections highlighted and numbered below represent the areas that designed with the error handling on data that are to be stored on the system. The numerals represented signify the specific position and the respective or corresponding error handling function attributed to the particular entry form before storage on the database. Data attributes for the database tables The information represents the features that enable for the information to be retrieved from or update to the current system database. Button Functions The snapshot below represents the buttons and their assigned functions embedded within the system program as exemplified on the interface. Each button will have a program that controls the actions when the button is clicked. Report for interface designed The interface designed has an automated process for documenting transaction reports and this feature is represented via the printing of a receipt within the system interface. The snapshot below symbolizes this particular feature. Program Design This section signifies the interface design of the buttons Structure Chart The figure below represents the structural design of the system on a chart based snapshot. Program Source code The code below is for the rental process module within the system. (Update_member module) Not_found = true If rental in table Retrieve details Display details not_found = false End if If button = save Update rental If not successful Display error Else if successful Display saved successfully message End if return Program Specification The program specification exemplified now is that for the process rentals within the systems functionality. The format offers a standardized arrangement for presenting an appropriate specification report. Inputs Outputs References Shelly, G. B., & Rosenblatt, H. J. (2012). Systems analysis and design. Boston: Course Technology Cengage Learning. Read More