Subject: System Development Method Submitted To: Ms Palvinder Kaur Date: 25th February 2013.
Submitted to:Ms Palvinder Kaur Lecturer of SDM
Submitted by:Arvind Kumar Reddy Hafiz Muhammed Owais Pavethra Ananthan
Table of Contents 1.0 INTRODUCTION ............................................................................................................................................... 3 2.0 SCHEDULE PLANNING ................................................................................................................................... 4 2.1 GANTT CHART................................................................................................................................................................... 4 2.2 PERTH CHART .................................................................................................................................................................. 4 2.3 WORKLOAD MATRIX ....................................................................................................................................................... 5 3.0 SELECTION OF METHODOLOGY ................................................................................................................. 6 3.1 SSADM.............................................................................................................................................................................. 7 3.2 STRUCTURED DEVELOPMENT OF LIFE CYCLE METHODOLOGY [ARVIND’S INDIVIDUAL] ................................. 11 3.3 RAD ................................................................................................................................................................................. 15 3.4 EVALUATION ................................................................................................................................................................... 18 4.0 PROBLEM ANALYSIS - CURRENT SYSTEMS ......................................................................................... 19 5.0 OVERVIEW - PROPOSED SYSTEMS ......................................................................................................... 20 6.0 PROCESS MODEL FOR PROPOSED SYSTEMS ................................................................................ 21 6. 1 CONTEXT DIAGRAM....................................................................................................................................................... 21 6.2 LEVEL 0 DFD ................................................................................................................................................................. 22 6.3 LEVEL 1 DFD FOR THE LEVEL 1 PROCESS................................................................................................................. 23 6.4 LEVEL 1 DFD FOR THE LEVEL 3 PROCESS................................................................................................................. 24 6.5 LEVEL 2 DFD FOR PROCESS 4 ..................................................................................................................................... 25 6.6 LEVEL 2 DFD FOR PROCESS 3 ..................................................................................................................................... 26 6.7 PROCESS SPECIFICATION .............................................................................................................................................. 27 6.7.1 Structured English .................................................................................................................................................... 27 6.7.2 Decision Tree ............................................................................................................................................................... 30 7.0 DATA MODELS FOR PROPOSED SYSTEMS........................................................................................... 31 7.1 ENTITY RELATIONSHIP DIAGRAM – LOGICAL DESIGN ............................................................................................ 31 8.0 DATA DICTIONARY FOR PROPOSED SYSTEMS .................................................................................. 32 8.1 ENTITY ............................................................................................................................................................................. 32 8.2 PROCESS .......................................................................................................................................................................... 32 8.3 DATA FLOW .................................................................................................................................................................... 33 8.4 DATA STORE ................................................................................................................................................................... 33 9.0 GRAPHICAL USER INTERFACE (GUI) .............................................................................................. 34 10.0 SYSTEM PROTOTYPE ............................................................................................................................... 35 11.0 REFERENCE ............................................................................................................................................... 36
1.0 Introduction The existing manual system being used in EasyRent Store business is lack of flexibility. This inflexibility manual system makes the business flow to run inefficiently and unproductively. In this case study, we are hired to develop an e-commerce website system for a video rental store, EasyRent operates within the city.
This system will help the management to computerise the working mechanisms that are being done manually recorded into books and spreadsheets. The main purpose of developing this system due to number of customer increases, with the same process as in the store, the management wishes to establish an e-commerce website to further expanding. Besides, through this system, paper work and human errors would be reduced. The database allows the management to check their stock or their inventory, which will make their company more effective. Thus, all gathered information will be stored in the system database therefore make sure its ease in retrieval and safety. This system will be the main tool for the company, because it solves a lot of problem in the company, which will increase the quality, and the efficiency of the company. So a lot of time will be saved and it will increase the customer requirement. As the result, it will make an improvement for the company. Hence, the software that we use to make this system like the design, the coding, we are using Microsoft excess to make the application become more user friendly.
2.0 Schedule Planning
Following shows the project schedule planning process, it uses Gantt chart, Perth Chart, and Workload matrix.
2.1 Gantt chart Gantt chart is a cross-platform desktop tool for project scheduling and management.
2.2 Perth Chart PERT chart is a graphic representation of a project’s schedule, showing the sequence of tasks, which tasks can be performed simultaneously, and the critical path of tasks that must be completed on time in order for the project to meet its completion deadline.
2.3 Workload Matrix Arvind K Reddy
Hafiz Muhammad
Pavethra
TP 023 281
TP 027 XXX
TP 027 XXX
Documentation 1.0 Introduction
50%
50%
2.0 Schedule Planning 2.1 Workload Matrix 2.2 PERT Chart
100% 100%
2.3 Gantt Chart
100%
3.0 Selection of Methodology 3.1 SSADM
100%
3.2 RAD 3.3 SDLC
100% 100%
4.0 Problem Analysis
33.3%
33.3%
33.3%
5.0 Overview of Proposed System
33.3%
33.3%
33.3%
50%
50%
6.0 Process Model 6.1 Context Diagram
100%
6.2 Data Flow Diagram Level0
100%
6.3 Data Flow Diagram Level1
100%
6.4 Data Flow Diagram Level2 6.4 Process Specification
50%
50%
50%
50%
7.0 Data Model 7.1 ERD 8.0 Data Dictionary 8.1 Data Flow
100%
8.2 Data Store
100%
8.3 Process
100%
8.4 External Entity 9.0 Graphical User Interface 10.0 System Prototype
100% 33.3%
33.3% 100%
33.3%
Total
33.3%
33.3%
33.3%
Signature
3.0 Selection of Methodology The early applications of computers and systems were largely developed without using any methodology. Those days, application is relies on programmer skills rather than communication. Methodology is a system that consist a set principles and practices. Each methodology has different principles and the way practices that use to solve different problem. Having a clear methodology is often important. (wisegeek.com, 2010) Three different methodologies were selected for comparison to choose the best suitable solution to problem; the three methodologies selected are SSADM, SDLC and RAD. That will be explaining as following.
3.1 Structured System Analysis and Design Methodology [Hafiz Individual] Structural analysis of the systems and methods of design, or SSADM, is a systematic approach to the analysis and design of information systems, which uses a combination of text and graphics throughout the entire life cycle of designing systems begin early design ideas for physical design. SSADM consists of seven stages of the life cycle of the project and at the end of each level, analysts and users can decide to move to the next level, resulting in a project, or select one or more levels. Scope To practice modelling work which to change the user's role as an important factor in determining the correct model of the system and methods of work. Purpose SSADM or analysis of the structure of the system and methods of computation are information systems development methodology. Learmonth and Buchett development management in early 1980, SSADM become a standard method for computer projects in the UK. Structure
6 Stages of SSADM Stage 1: Investigate the current environment Draw a data flow diagram (DFD) and the logical data model (LDM), shows the current system. Logical Data Model (LDMS) is similar to the entity-relationship diagram (ERD).
Stage 2: Business Systems Options (BSOs) Describe the system may be new in terms of functionality and implementation issues by Using text DFD frame and LDMS.
Stage 3: Requirements Specification After you select the BSO, BPB and explain LDMS. To simulate how the system will behave reply to events (model the behaviour of it), the life story of the painting person (ELH), persist power, and query access passes (EAP).
Stage 4: Technical System Options (TSOs) Describe the costs, benefits and limitations of implementing specifications.
Stage 5: Logical Design Determine how the data is processed by the system and describe the user dialog. Updates cart someone's life history with status indicator and a processing model (UPM).
Stage 6: Physical Design Structure development and implementation process of the user interface logic.
How your project will be developed according to the methodology
1. The existing business flow is evaluated. The lacking is identified. This can be done by observing the business flow, consulting the management.
2. The new system requirements are defined especially the shortage and the limitations in the business flow have be addressed with specific proposals for the new e-commerce online system.
3. The proposed system is designed. Plans are arranged concerning the tangible construction, hardware, operating systems, communications, security issues and programming.
4. E-commerce online system is developed. The programs and components must be installed and obtained. The users’ must be trained in its usage and all aspects of performance must be tested before hand over to the management. If there are possibilities, adjustments must be made at this stage itself.
5. The e-commerce online system is placed for use.
6. Once the online system is up and running for a while, it should be fully evaluated. Hence, maintenance must be kept thoroughly at all times to prevent spam and hacking or lost of data. Management should be kept up-to-date concerning the latest procedures and modifications.
Strengths of SSADM Improved project management and self-documentation, SSADM also leads to reduced project costs due to higher quality analysis and system design, improved communication and increased staff effectiveness. Well documented. Ensure deliver the project on time Usability where SSADM is special emphasis on the analysis of user needs Respond to change in the business environment Effective use of skills that use common modelling and diagramming tools. SSADM reduce the error rate of IS by checking quality of system within progress of development to provide better quality system. Weakness of SSADM
Lack of user involvement means the system rarely meets user needs and is less likely to be accepted. It takes a great deal of time to complete project Costly due to Heavy procedures and stages. SSADM is built on the analysis of data, if this data change after the SSADM analysis, the system development might be going wrong.
3.2 Structured Development of Life Cycle Methodology [Arvind’s Individual]
A Software Development Life Cycle (SDLC) is a fundamentally of phases that presents a model for the development and lifecycle management of an application. It is also known as a framework defining tasks performed at each phase in the process that consists in detail on how to develop, maintain and replace specific software. The life cycle describes a methodology for improvements upon the software and the process in the development. Scope The scope of a SDLC in EasyRent Online Video Rental System is to help in producing an online service effectively, efficient in cost and with high quality. SDLC methodology contains the following stages; analysis, construction, testing, release and maintenance. Purpose Depending on which industry you work in the SDLC, there are many variations to the SDLC but they are sharing the same focal point tricks as below;
1) What deliverables must be created? Work of arts are the modules, tasks, documents, items and many more that are created for a new project.
2) How deliverables would be created? Analysts will identify how deliverables are developed, assign tasks properly and determine what methodologies and processes to use in order to help complete tasks and deliverables.
3) Who will create the deliverables? A project manager identifies individuals who will complete the tasks and deliverables according to the needed skill sets.
4) When will be created? Analyst would develop a project schedule or timeline and deliverables and tasks will be determined and recorded in that.
5) Where everything will be documented? An analyst gathers and documents the answers to the above questions. Structure
The Waterfall life cycle model is a model that involves concluding the first step completely before proceeding to another phase. And when each phase is successfully completed, it is reviewed to see if the project is feasible to continue or going on flow.
The SDLC encompasses 6 phases which may combine or may overlap; 1. Planning Phase The concept is further developed to describe how the business will operate once the online system approved and implemented and to assess how the system will impact the privacy of business and customer.
2. Requirements Analysis Phase All requirements are defined to a point of detail enough for system designing to continue. Also, need to be measured and testable and relate to the EasyRent business need.
3. Design Phase The substantial characteristics of the online system are designed during this phase. The operating environment is created, subsystems, inputs and outputs are also created and the processes are divided to resources. Thus, all requiring user input or authorization must be documented and evaluated by the management.
4. Testing Phase This is the process of finding bugs and defects in the software and various components in the system are integrated and systematically tested. The user tests the system to ensure the user meets his requirements upon the system as defined in the functional document.
5. Implementation Phase The system and its modifications are installed and made operational in a production environment. The phase is initiated after the system has been tested and approved by the user. Thus, this phase continuous until the system is operating in production with the user requirements.
6. Maintenance Phase The software is deployed after it has been approved by the tester and operational managers for release.
How your project will be developed according to the methodology
7. The existing business flow is evaluated. The lacking is identified. This can be done by observing the business flow, consulting the management.
8. The new system requirements are defined especially the shortage and the limitations in the business flow have be addressed with specific proposals for the new e-commerce online system.
9. The proposed system is designed. Plans are arranged concerning the tangible construction, hardware, operating systems, communications, security issues and programming.
10. E-commerce online system is developed. The programs and components must be installed and obtained. The users’ must be trained in its usage and all aspects of performance must be tested before hand over to the management. If there are possibilities, adjustments must be made at this stage itself.
11. The e-commerce online system is placed for use.
12. Once the online system is up and running for a while, it should be fully evaluated. Hence, maintenance must be kept thoroughly at all times to prevent spam and hacking or lost of data. Management should be kept up-to-date concerning the latest procedures and modifications.
Waterfall Strengths of SDLC Easy to understand and use. Makes tasks more manageable Targets are well understood. Sets requirements stability and provides standards for documentation. Works well when quality is more important than cost.
Waterfall weakness of SDLC Can give a false impression of progression Doesn’t reflect the nature of problem solving of software development (Iterations of Phases) All requirements must be known outspoken Deliverables developed for each phase are considered solid.
3.3 Rapid Application Development [Pavethra’s Individual] RAD term is introduced in 1991 by James martin to describe the software development methodology that involves short iterations and depends in part on the prototype to complete the requirements specification. In recent years, the reduction has been used in a broader sense and includes a set of methods (such as the use of the framework), which aims to accelerate the development of applications. RAD is often used in situations where time constraints forced an approach where a faster application development takes priority over the full functionality and performance.
Scope If the amounts of focused and clear business goals are narrow, then the project is suitable for RAD. On the other hand, if the scopes of the business objectives are not clear or large the project is not suitable for RAD.
Purpose Rapid Application Development (RAD) is a method to develop a system using joint application development (for user input), prototyping, CASE technology, application generators, and similar tools to speed up the design process.
Structure
RAD life cycle of the structure is designed to provide developers build systems that users really need. This life cycle, based on the following four stages, includes all activities and tasks required to determine the scope and business requirements and design, develop and implement an application system that supports these requirements: Š Requirements Planning Also known as the concept definition phase, this phase defines the business functions and the data subject that the system will support and define the scope of the system Š User Design Also known as the functional design stage, at this stage uses workshops to model the system and process data, and to create a working prototype of critical system components.
Construction
Also known as the stage of development, this phase is completed the construction of physical applications, build a conversion system, and develop a user manual and a plan for implementation of the work.
Implementation
Also known as the deployment phase, this section includes an end-user testing and training, data conversion, and implementation of application systems. How your project will be developed according to the methodology
1. The time required to develop the software is drastically reduced due to a reduced requirement analysis business requirements documentation and software requirement specification) and planning stage. 2. All the software prototypes produced can be kept in a repository for future use. The reusability of the components also enhances the speediness of the process of software development. 3. It is much easier for a project manager to be accurate in estimating project costs which of course means that project cost controls are easier to implement and manage as well. 4. It is a big cost saver in terms of project budget as well as project time and cost due to reusability of the prototypes. 5. If a component is being picked for the repository, it is already tested and hence need not be tested again. This helps in saving time required for testing. 6. The project management requirements are collected in a dynamic manner. Every time there is a prototype ready, requirements are studied and matched. If there are any additional requirements, these are then included in the next prototype built. 7. There is a strong and continuous participation of the project sponsor who keeps giving feedback in the whole process. Hence the end user satisfaction level is higher when the end result is produced. 8. It promotes better documentation through written test cases
Strengths of RAD Application for rapid development. Improved quality (according to the RAD, quality is defined as the degree of delivered user needs, and the extent to which the system has delivered lower operating costs). Speed up development of the system. Improving the quality that meets the needs of users and have low maintenance cost. Weakness of RAD Scalability is reduced, while it is not intended as a full application from scratch Less featured than traditional methods of development Depends on strong team and individual performances for identifying business requirements. Only system that can be modularized can be built using RAD. Requires highly skilled developers/designers.
3.4 Evaluation There are many methodologies available today that used to solve different problem. After series of understanding and research, my group have select SSADM method for our project. Moreover, SSADM method provides better quality systems that reduce the errors which can cause business transaction interrupt and business reputation lost. From the comparison of methodologies, SSADM is believed to be the best suitable solution for the EasyRent Video Store sales and online system development.
4.0 Problem Analysis - Current Systems Brief analysis of the current system including description of the constraints and opportunities for the proposed system
Manually human work is the main problem. EasyRent Online Video Rental System is a noncomputerised management system which operates within the city. Currently all data in the store are manually recorded into books and spreadsheets. The store personnel are responsible for recording the details of all transaction occurring in the store. The managers in the store will monitor this information from time to time. The management noticed that number of customer increases. So, the management grabs the opportunity and wishes to establish an e-commerce website to further expand their business. The website will feature the same process as in the store. In order to fulfil the business’ needs and flexibility in business, the management realised the need for a new efficient system where upon order, the online customer’s videos will be posted to their home by the store. Once done, the customers can post it back to the store within two weeks. EasyRent video could be the top compare with other video rental shop. They have many higher goals, requirements, and vision that are:-
Developing a newer and efficient system better than current system. Enlarge the business marketing of video rental to other city. Build up a friendly environment to customers. The number of customers increases to 30%.
5.0 Overview - Proposed Systems An explanation of how the systems solve the existing problems and addresses opportunities.
The proposed system will serve as an online system where customer just need to register through online for membership and can make orders from there and the system will take care the rest of the process and employees will post the requested items. However upon order, the online customer’s videos will be posted to their home by the store.
A work flow will be like example below: A customer applies for membership to become a member if they aren’t a member, which includes a rental deposit. Then, the system update the customer database and back to the customer for requesting item. The customer will place maximum three movies at a time for a period of one week. Thus, a standard rental fee will be imposed for each item depending on the type. After placing an order, the system will check if the movie is still in store and tells the customer. Then, if the requested movie is there, it’ll go to the next process which is payment. Customer can make payments through credit card and system would check for validation if it’s still active and proceeds to the next processes which are done by the employees in the store after the customer returns the rented videos through post or at the store itself. With the proposed online system, it will also shorten the time of sales and it can get more business with it since online transactions are becoming more efficient and compact for people.
All the new customer detail will be updated in the computer database by the system while new purchased videos detail can be key in the database by employees. It will save more employees’ time on serving a lot of customers in the shop due to the number of customer increases.
6.0 Process Model for Proposed Systems 6. 1 Context diagram
6.2 Level 0 DFD
6.3 Level 1 DFD for the Level 1 process
6.4 Level 1 DFD for the Level 3 process
6.5 Level 2 DFD for process 4
6.6 Level 2 DFD for process 3
6.7 Process Specification Data flow diagrams do not show the logic inside the processes. Process Specification involves representing internal structure and functionality of processes depicted on a DFD. Process Specification can also be used to show when processes on a DFD occur. 6.7.1 Structured English
Structured English is used to describe input and output. Structured English is used to describe arithmetic Operations. Structured English is used to describe repetition. Structured English is used to describe decisions. Structured English is used to describe invoking other processes.
Process 1.0: Apply Membership IF customer wants to apply membership Gather data from the customer and store in customer database IF customer username is unique Give membership card and enable them to login the website.
ELSE
Send a notification to the customer to apply membership IF new membership registration is received Send membership notification END IF END IF END IF EXIT
Process 2.0: Rent Video IF customer wants to rent a video
THEN retrieve member information from customer database
Retrieve rented movie from video renting file Give access to search from video renting file Give access to rent movie ELSE reject
IF customer request to rent a movie THEN check for rental deposit from rental file and send availability movie information from video renting file. Allow customer to rent the movie. ENDIF ENDIF EXIT
Process 3.0: Make Payment IF customer pays the amount for the video that they rented
THEN take the credit card from the customer Retrieve rented movie from video renting file
ELSE reject IF customer’s credit card is not valid or approved THEN notify the customer ENDIF ENDIF EXIT
Process: 4.0 Return Video IF the customer return the video Collect the rented video and membership card THEN update rental details in video renting file
ELSE IF The customer does not return the video at time THEN apply penalty charge and update transaction file END IF EXIT
Process: 5.0 Buy New Video IF the distributor send the new video catalogue THEN management sends the list of new videos to the supplier and return obsolete videos ELSE IF The requested video has been received THEN update the video details in video renting file END IF EXIT
Process: 7.0 Generate Daily Report IF daily report needs to be submitted to manager THEN Retrieve all transactions made from video renting file and transaction file Generate the report and send to manager
EXIT
6.7.2 Decision Tree
Is a graphical representation of the conditions, actions and rules found in a decision table to show the logical structure in a horizontal form that resembles a tree with the roots at the left and the branches to the right also an effective ways to present the system to the management?.
7.0 Data Models for Proposed Systems 7.1 Entity Relationship Diagram – Logical Design
8.0 Data Dictionary for Proposed Systems 8.1 Entity Name:
Manager
Description:
Manager receives daily reports to have a successful supervision on the system and the business flow.
Input Data Flow:
Daily Rental Record, Payment Transaction
Output Data Flow:
-
8.2 Process Name:
5.0 Generate Daily Reports
Description:
Generate daily report from video renting file and transaction file for manager.
Input Data Flow:
Daily Rental Info, Get Payment Transaction.
Output Data Flow:
Daily Rental Record, Payment Transaction.
Process description:
IF it is the last working day and also last hour THEN Retrieve all information about rented and received items from video renting file and payments from the customer from the transaction file. Generate a daily report for manager. END IF EXIT
8.3 Data Flow Name:
Customer details
Description:
Detail of customers who wish to register to this system
Origin/Source:
Customer
Destination/Sink:
1.1 Receive customer details
Data structure:
Customer name, Address, Phone, E-mail address, Customer ID(user name and password), Date of birth
8.4 Data Store Name:
Customer data base
Description:
Stores registration details and give updated customer list to other processes.
Input data flows:
Customer Details, Renting Status
Output data flows:
Customer Information
Data structure:
Customer ID, Customer name, Address, Telephone, Status
9.0 Graphical User Interface (GUI)
10.0 System Prototype
11.0 Reference 1. Wisegeek.com
(2010)
What
Is
Methodology?
[Online]
Available
from
http://www.wisegeek.com/what-is-methodology.htm [Accessed 3 January 2013] 2. Casemaker.com (2000) What is Rapid Application Development (RAD) [Online] Available fromwww.casemaker.com/download/products/totem/rad_wp.pdf[Accessed 3 January 2013] 3. System Analysis And Design (1998) [Online] Available from http://www.eis.mdx.ac.uk/staffpages/geetha/bis2030/DFD.html[Accessed 3 January 2013] http://www.hit.ac.il/staff/leonidm/information-systems/ch32.html http://www.casemaker.com/download/products/totem/rad_wp.pdf http://www.novulo.com/Rad.aspx http://upload.wikimedia.org/wikipedia/commons/thumb/5/5f/RADModel.JPG/320pxRADModel.JPG http://www.smartdraw.com/resources/tutorials/ssadm-diagrams/ http://www.grin.com/en/e-book/106034/the-use-of-ssadm-structured-systems-analysisand-design-methodology-as http://microinnovationsnetworkcard.danielcadams.com/advantages-and-disadvantagesof-ssadm/ http://www.selectbs.com/analysis-and-design/what-is-ssadm
