ACS2913 Software Requirements Analysis And Design Project Example PDF

ACS2913 Software Requirements Analysis and Design PROJECT EXAMPLE THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 1 From Beginning to End: Sample Project Sample small information system application to demonstrate how all six core processes are used in one actual working proje...

ACS2913 Software Requirements Analysis and Design PROJECT EXAMPLE THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 1 From Beginning to End: Sample Project Sample small information system application to demonstrate how all six core processes are used in one actual working project The project involves Ridgeline Mountain Outfitters (fictitious company), retailer, manufacturer of clothing for outdoor activities. Large Retail Company ◦ outdoor and sporting clothing and accessories ◦ Skiing, mountain biking, water sports ◦ Hiking, camping, mountain climbing Continuous growth ◦ Form mail-order, to brick-and-mortar, to online sales ◦ Most sales specific to the western region of the US, but other areas growing ◦ Most growth happens from online offerings THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 2 Tradeshow System for RMO RMO’s purchasing agents attend apparel and accessory trade shows around the world At these events, purchasing agents find various products to add to their seasonal apparel offering To expedite orders, RMO has initiated a project to develop a system for collecting and tracking information about its suppliers, and the new products it adds to its merchandise offerings. THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 3 RMO Tradeshow System Sample project for chapter Small information system (app) Being added to larger supply chain management system Demonstrates one iteration of the small project – assumes more iterations in total project THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 4 RMO Tradeshow System Problem-- purchasing agents attend apparel and fabric trade shows around the world to order new products from suppliers Need– information system (app) to collect and track information about suppliers and new products while at tradeshows Supplier information subsystem Tradeshow Project– is proposed Product information subsystem THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 5  RMO Tradeshow System Project Goes through all six core processes of SDLC assume one process per day THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 6 Initial Activities – Core Process1 Identify the problem and document the objective of the system Preliminary investigation What problem or opportunity is the project meant to address? What are the high-level objectives you want to achieve with the new system? Feasibility analysis (Technical, Economic, Legal/Regulatory) Assemble a Project Team: End-users, IT professionals, management, and any other relevant parties. Scope Definition: What are the boundaries of the system you are planning to develop? What functionalities and features should be included? What should be excluded? Cost Estimation → System Vision Document Obtain approval to commence the project Meet with key stakeholders, including executive management Decision reached, approve plan and budget THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 7 System Vision Document Problem description System capabilities Business benefits See textbook page 13 THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 8 Day 1 Activities Core Process 2: Plan the Project Determine the major components (functional pieces) that are needed Supplier information subsystem Product information subsystem Define the iterations and assign each function to an iteration Decide to do Supplier subsystem first Plan one iteration as it is small and straight forward Determine team members and responsibilities THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 9  Work Breakdown Structure I. Discover and understand the details II. Design the components of the of all aspects of the problem solution to the problem 1. Meet with the purchasing depart 1. Design input screens, output screens, and manager ~3hrs reports ~6 hrs 2. Meet with several purchasing agents ~ 4 2. Design and build database ~4 hrs hrs 3. Design overall architecture ~4hrs 3. Identify and define use cases ~3hrs 4. Design Program details ~6 hrs 4. Identify and define info requirements ~2 hrs 5. Develop workflows and descriptions for the use cases ~6 hrs THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 10 WBS III. Build the components and integrate everything into the solution 1. Code and unit test GUI layer ~14 hrs 2. Code and unit test Logic layer programs ~8 hrs 3. Perform all system-level test ~ 5 hrs 4. Perform functionality tests ~5 hrs 5. Perform User acceptance test ~8 hrs THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 11 Day 2 Activities Core Process 3: Discover and Understand Details ◦ Do preliminary fact-finding to understand requirements ◦ Define the requirements for the information system. This includes functional, non-functional, and stakeholder-specific requirements. ◦ Gather Documentation: ◦ Collect all relevant documentation about the information system, such as system architecture diagrams, process flowcharts, data models, user manuals, and any existing analysis or reports. ◦ Conduct Interviews and Surveys: ◦ Interview key stakeholders and users to gather their perspectives on the system's strengths, weaknesses, and pain points. ◦ Distribute surveys or questionnaires to a broader audience to collect quantitative data and feedback. THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 12 Supplier Information Subsystem Develop a preliminary list of use Use cases: cases and a use case diagram Look up supplier Enter/update supplier information Lookup contact information Enter/update contract information THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 13 Identify Use Cases Both subsystems THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 14 Use Case Diagram Supplier information subsystem Displays actors, and use cases THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 15  Activity Diagram (Workflow) Core Process 3: Discover and Understand Details ◦ Do in-depth fact-finding to understand requirements ◦ Understand and document the detailed workflow of each use case Look up supplier use case THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 16 Identify Object Classes Both subsystems ◦ Develop a preliminary list of classes and a class diagram THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 17 Preliminary Class Diagram Both subsystems THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 18  Day 3 Activities Core Process 4: Design System Components ◦ Define the user experience with screens and report sketches THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 19 Draft Screen Layout Look up supplier use case THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 20 Day 4 Activities Core Process 4: Design System Components ◦ Design the database (schema) ◦ Table design ◦ Key and index identification ◦ Attribute types ◦ Referential integrity ◦ Design the system’s high level structure ◦ Browser, Windows, or Smart phone ◦ Architectural configuration (components) ◦ Design class diagram ◦ Subsystem architectural design THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 21 Architectural Configuration Diagram THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 22 Design Class Diagram Includes View Layer Classes and Domain Layer Classes THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 23 Subsystem Architectural Design Diagram THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 24 Notes on Managing the Project Lots of design diagrams shown ◦ Design in a complex activity with multiple levels ◦ One diagram builds on/complements another ◦ Not everything is diagrammed, especially for a small project. Pick and choose. Programming is also done concurrently ◦ You don’t design everything then code ◦ You do some design, some coding, some design, some coding THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 25 Day 5 Activities Core Process 4: Design System Components ◦ Continue with design details ◦ Proceed use case by use case Core Process 5: Build, Test, and Integrate System Components ◦ Continue programming (build) ◦ Build use case by use case ◦ Perform unit and integration tests THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 26  Code Example for One Class THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 27 Day 6 Activities Core Process 6: Complete System Testing and Deploy the System ◦ Perform system functional testing ◦ Perform user acceptance testing ◦ Possibly deploy part of system THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 28 Workflow of Testing Tasks THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 29  This was a 6 day iteration of small project Most iterations are This project might be Most projects have longer (2 to 4 weeks) 2 iterations many more iterations First Iteration End users need to be involved, particularly in Recap day 1, 2, 3 and 6. Days 4 and 5 involved design and programming concurrently. THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 30 This Course is about Activities and Tasks in the SDLC THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 31 Summary Topics to review ◦ System vision document ◦ Work breakdown structure ◦ Work sequence draft ◦ Use cases ◦ Use case diagram ◦ Object classes (domain classes) ◦ Class diagram ◦ Design class diagram ◦ High level structural design (architectural design) ◦ Database schema ◦ Screen layout THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 32