This document provides an overview of system analysis and design, focusing on the Scrum, Extreme Programming, and Waterfall Model methodologies. It includes use case diagrams, domain model class diagrams, and a case study on the implementation of a management information system. The importance of HCI and UCD in system design is also discussed.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: SYSTEM ANALYSIS AND DESIGN System Analysis and Design Name of Student- Name of University- Author’s Note-
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
2SYSTEM ANALYSIS AND DESIGN Table of Contents 1. Consultation.....................................................................................................................3 1.1 SCRUM.....................................................................................................................3 1.2 Extreme Programming:..............................................................................................4 1.3 Waterfall Model:........................................................................................................5 2. Analysis of Case..............................................................................................................7 Event Table......................................................................................................................7 Use case diagram.............................................................................................................9 Use Case description......................................................................................................10 Domain Model Class Diagram......................................................................................11 Class diagram for Associate Broker and order..............................................................12 3. Memo.............................................................................................................................12 Bibliography......................................................................................................................15
3SYSTEM ANALYSIS AND DESIGN 1. Consultation 1.1 SCRUM The Scrum is one of the extensively used agile SDLC model. The Scrum is famous for supporting both the incremental and iterative software development structure. The Scrum has successfully handled the drawbacks of the conventional SDLC model and provided a dynamic approach toward software development. In order to introduce flexibility, productivity and adoptability, the Scrum model was developed based on process control theory. The adaptation, transparency and inspection are the main three features of the Scrum that makes it suitable for big and complex projects. The Scrum methodology has three phases, such as pregame, game and postgame. In the pregame phase, the project vision is defined. Along with the vision, the functional and non-functional requirements are defined by the product owner. The product backlogs are the required features of the product1. Based on the development plan of each feature of the final products release plan is developed. In the game phase, the actual development work is done. The game phase is completed through executing small iterations called sprints sequentially. One sprint can be time period of one week to four weeks, based on the complexity of the work. Each sprint has four parts like develop, wrap, review and adjust. The postgame is the closure phase of the project. The final release happens when the intended works have been completed. The final integration testing is done in this project phase. The training materials and user manuals are also created in the postgame phase. 1Anwer, Faiza, Shabib Aftab, SS Muhammad Shah, and Usman Waheed. "Comparative Analysis of Two Popular Agile Process Models: Extreme Programming and Scrum."International Journal of Computer Science and Telecommunications8, no. 2 (2017): 1-7.
4SYSTEM ANALYSIS AND DESIGN The Scrum methodology is controlled by three roles mainly such as product owner, scrum master and team. The product owner are generally the client representative who takes the out of the scope decisions. The Scrum master monitor and control all the scrum related activities. The team collect data, analyse data, create design, development software and test the software. Advantages i.The usage of time and capital is handled effectively and efficiently ii.The coding and testing is done during the sprint review iii.The short period of sprints allow adjustment in the development software quickly iv.The fast-moving software development projects are best suited2 v.The scrum meetings are very assisting in sharing the clear picture of the project Disadvantages i.The scrum has a bad reputation of leading the projects to scope creep ii.Can be done by only skilled and experienced experts who charge a lot of capital iii.The daily meetings often hamper the workflow iv.The quality of final product is often compromised as the new scopes are hard to align with the project objective 1.2 Extreme Programming: Extreme programming is also another agile software development model. The extreme programming is very lightweight and it is more flexible than Scrum. The extreme programming can easily capture the rapid changing requirements and integrate those changes into project. The extreme programming focuses its time on the coding part and reduces the amount of planning 2Edeki, Charles. "Agile Software Development Methodology."European Journal of Mathematics and Computer Science Vol2, no. 1 (2015).
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
5SYSTEM ANALYSIS AND DESIGN and requirement gathering. The extreme programming phases are exploration phase, planning phase, release phase, iteration planning, iteration to release phase, productionizing phase, maintenance phase and death phase. Advantages i.The extreme programming is very fast and it is quickly completed than other methodologies ii.The cost of the development is also very low than other methods iii.The communication among the team is extremely good and it allows all members to have proper idea of the project insights iv.The methodology focuses on increasing teamwork Disadvantages i.There is a possibility that customer may not be happy with the final product as the extreme programming does not focus on designing ii.This methodology does not concentrate on documentation which increases the possibility of unexpected failures iii.As the deadline is tight, the team can be under immense pressure and may not provide good quality work 1.3Waterfall Model: Waterfall model also known as the linear-sequential life cycle model is the very first process model that was introduced and is known as the earliest SDLC (Software Development Life Cycle) approach in the software development field. The process involves logical sequential
6SYSTEM ANALYSIS AND DESIGN flow, this implies that without completing the previous development process the next phase cannot be approached and thus, reducing the overlapping of the phases. The Waterfall model comprises of mainly six stages which are, the requirement phase, then comes the analysis of the requirement, the designing of the software comes after that, coding and testing are the next two phases in this cycle and the last stage is the deployment of the developed software. In the requirements phase, a requirement document is created by the developers listing every possible requirements. The functions of the system are defined in this document and is used in the future development. The analysis stage is used by the developers to analyse the requirements and draw the logical design for the system without any hardware and software specifications. In the next phase, the logical design is altered according to the hardware and software requirements for the system. The coding stage comes right after this, where the actual coding for the required system is written3. The testing stage involves the quality checking of the developed system, with the help of quality analyst, beta tester in order to report any bugs in the system. The last stage, the deployment stage involves the release of the system in the market, providing customer support, maintenance of the system and future up gradation to meet the requirements of the customers. Advantages i.Better understanding of the errors and system. ii.The process defines milestones which will help the developers to create definite and concrete goals for the project 3Chi,C.2019.EverythingYouNeedtoKnowAboutUsingtheWaterfallMethodology.[online] Blog.hubspot.com.Availableat:https://blog.hubspot.com/marketing/waterfall-methodology[Accessed28Jun. 2019].
7SYSTEM ANALYSIS AND DESIGN Disadvantages i.The developers cannot move to the next stage without completing the previous one. ii.The requirement cannot be changed later. Recommendation: As per the requirements of Australian Electric Supply, the scrum model is the most suitable methodology for developing the information system. The Scrum will allow the organization to include staff, customer and other end users into the project. The final product can be customer centric. As the system will be developed in pieces, Australian Electric Supply will have working software from early stages of the development project. 2. Analysis of Case Event Table EventEvent Type TriggerSource Actor Use CaseOutputDestination actor Generate new customer detail ExternalNew Customer CustomerSign upNew customer detailsare enteredinto the system Customer Verify customer account ExternalCustomer verification CustomerSign InSystem allows authentication tousethe Customer
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
8SYSTEM ANALYSIS AND DESIGN functions Customer makea new order ExternalPossible product sales CustomerPlace Order Customer orderis confirmed andsentto warehouse Warehouse Employee
9SYSTEM ANALYSIS AND DESIGN Use case diagram Figure 1: Use Case Diagram (Source: Created by author) Use Case description Use Case NameApply Coupon
10SYSTEM ANALYSIS AND DESIGN Use Case IDCust_UC_04 ActorsCustomer PreconditionThere must be items in the cart before coupon can be applied ActivitiesActorSystem Customer add products to cartSystem checks item availability Customer click on proceedSystem redirect to another page Customerentercouponcodein particular area System check coupon validity and reduce the coupon amount Customer see updated cost Post conditionCustomer can use coupon only once ExceptionSystem does not approve code for specific items
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
11SYSTEM ANALYSIS AND DESIGN Domain Model Class Diagram Figure 2: Class Diagram (Source: Created by author)
12SYSTEM ANALYSIS AND DESIGN Class diagram for Associate Broker and order Figure 3: Class Diagram for associated broker and order (Source: Created by author) 3. Memo Date: June, 28, 2019 To: The Executive Analyst From: The Business Analyst of Australian Electric Supply (OZES) Subject: Implementation of Management Information System in OZES
13SYSTEM ANALYSIS AND DESIGN I want to inform you that our company OZES is working on an information system that will manage the whole second hand selling business process of our company OZES. We are currently working on the implementation of the information system in the company and we hope to finish the whole development and implementation of the information system within a period of 6 to 9 months from today. HCI or Human-Computer Interaction is the field of education that focuses on the computer design and the technologies and mainly focuses on the human interaction or the user interaction with the computer. The HCI provides a wide scope as well as includes the fields of the UCD or the user center design. Using the HCI and the UX Design enables then designers or the professionals to focus on the design based on the needs of the user. In this case, the main focus are the customers and also includes the usability of the system by the warehouse staffs, the associate broker and the management of the OZES. The system is designed in such a way that the users can understand any process very easily. Iterative process is used for the design of the system. The process will ensure the design is mainly focused on the needs of the user and the requirements of the user are collected and implemented in each design phase. The UCD essentially, involves the user during the design phase and the whole design process and many other research methods during the system design. The UCD provides high flexibility and usability for the users of the system and also provides high convenience and a very user-friendly environment for the users while they are using the system to search any product or service. The mix investigation process helps the designers and the developers to better understand the needs of the user. Other methods like the generative method also helps in the process of understanding the user needs and the method is accompanied by numerous other tools.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
14SYSTEM ANALYSIS AND DESIGN There are primarily four phases in the UCD, which includes the understanding on which context the system will be used, identification of the user needs or the requirement by the user, providing a proposed design or solution of the system based on the collected data and lastly, evaluating the requirements that are needed to build the proposed system. The OZES information system is mainly focused on the purchasing customers of the second hand selling product, selling customers of the second hand products, the brokers of the organization who are associated with the selling of a product and the whole management of the OZES. Surveys and interviews were conducted to collect data by the users of the system, there were active participation from the users. These data were analyzed and used to improve the design of the information system.