RMO Tradeshow System Quiz

Course Information

• Course title: Software Requirements Analysis and Design
• Course code: ACS2913
• Academic term: Fall 2024
• Institution: The University of Winnipeg

Project Example: Ridgeline Mountain Outfitters

• A fictitious company, a retailer and manufacturer of outdoor clothing
• The project involves a small information system application that uses all six core processes of the Software Development Life Cycle (SDLC)
• The company's business involves selling outdoor and sporting clothing and accessories
• The business has experienced continuous growth, transitioning from mail-order to brick-and-mortar to online sales
• Most sales are concentrated in the western region of the US.

Tradeshow System for RMO

• RMO's purchasing agents attend trade shows worldwide to find new products and add them to their seasonal apparel
• To streamline orders, RMO aims to develop a system to collect and track information about suppliers with the new products they are selling
• This project is part of a larger supply chain management system

RMO Tradeshow System Project

• The core problem that the project addresses is the difficulty of RMO's purchasing agents in acquiring information on suppliers and new products at tradeshows to meet their seasonal apparel needs
• The solution proposed is to use an application (app) that can collect and track requested information about suppliers and new products at tradeshows
• This will involve a Supplier Information Subsystem and a Product Information Subsystem

Project SDLC Processes

• The project will go through all six core SDLC processes
• The assumption is that one process will be completed per day

Initial Activities - Core Process 1

• Preliminary investigation: define the problems, opportunities, project objectives, high-level goals
• Feasibility analysis (technical, economic, legal/regulatory aspects)
• Create a project team including end-users, IT professionals, and management
• Scope definition: outlining system boundaries, including features, functionalities, and exclusions
• Cost estimation
• Develop a system vision document, securing approval from key stakeholders

System Vision Document

• The document describes the problem and the objectives of the Tradeshow System
• The document outlines the system's features as well as how these features aim to enhance the company's efficiency

Core Process 2: Plan the Project

• Determines the major components needed (functional pieces) for the project
  • Supplier information subsystem
  • Product information subsystem
• Defines iterations and assigns functions to each iteration
• Performs fact-finding to understand requirements, including stakeholder-specific requirements
• Gathers documentation about the system, such as architecture diagrams, process flowcharts or reports.
• Interviews stakeholders and conducts surveys
• Distributes surveys and questionnaires to collect quantitative data

Work Breakdown Structure

• Detailed tasks to discover, understand, and plan for all aspects of the problem
  • Meeting with purchasing department managers
  • Meeting with purchasing agents
  • Identifying and defining use cases
  • Understanding information requirements
  • Developing work flows for use cases

Build the Components and Integrate (WBS)

• Coding and unit testing the GUI layer, logic layer programs, performing all system-level tests, functionality tests, and user acceptance tests tasks

Day 2 Activities

• Preliminary fact-finding to understand the requirements
• Defining the requirements for the information system which includes functional, non-functional requirements, and specific requirements for stakeholders
• Gathering relevant documentation for the system (including architecture diagrams, process flowcharts, user manuals, analysis reports)
• Conducting interviews and surveys to collect detailed perspectives about the system's strengths, vulnerabilities and pain points
• Distributing questionnaires and surveys to gather quantitative data and feedback for a broader audience

Supplier Information Subsystem Tasks

• Developing a preliminary list of use cases, including a use case diagram
  • Examples of use cases include: look up supplier, modify supplier information, look up contact information etc

Identify Use Cases (Both Subsystems)

• Detailed descriptions of use cases for both subsystems

Use Case Diagram (Supplier Subsystem)

• Diagram that displays actors and their corresponding use cases for Supplier Information Subsystem

Workflow of Testing tasks

• Step-by-step instructions for carrying out testing tasks, from creating test data to conducting tests, documenting errors, and fixing them

Day 4 Activities

• Designing the database schema
• Creating table design
• Identifying and outlining key aspects and indexing
• Defining attribute types
• Incorporating referential integrity
• Developing a high-level architectural configuration
• Developing a browser, Windows, or smartphone configuration
• Drawing the class diagram to detail the design of the system
• Outlining subsystem architectural design

Architectural Configuration Diagram

• A diagram illustrating the system's architectural configuration

Design Class Diagram

• Diagram outlining view layer classes, domain layer classes, and relationships
• Features of the Supplier Class: supplierID, name, address, address2, city, state, country, URL, comments
• Features of the Contact Class: contactID, name, title, address1, address2, city, state, postal, country, phone etc.

Subsystem Architectural Design Diagram

• Diagram explaining the supplier subsystem and domains

Notes on Managing the Project

• Notes for managing the project, including design diagrams
• Notes on concurrent programming

Day 5 Activities

• Continuing design details
• Creating use cases one by one to create use cases
• Building and performing unit and integration tasks

Code Example for One Class

• A code example illustrating the code structure for one class in the project

Day 6 Activities

• Performing a complete system test
• Carrying out user acceptance testing
• Considering the possibility of partially deploying the tested system

Workflow of Testing tasks

• A visual representation of the sequence of actions to be taken for any testing tasks

First Iteration Recap

• Six Days as time limit from the inception of the project
• Involving end users for effective feedback
• Concurrent design and programming in days 4 and 5

This Course is about Activities and Tasks in the SDLC

• Short summary of SDLC processes and iterations

Summary of Topics to Review

• Review of critical topics such as the system vision document, work breakdown structure, use cases, use case diagrams, object classes, class diagrams, design class diagrams, database schema, and screen layouts.

Test your knowledge about the Ridgeline Mountain Outfitters (RMO) Tradeshow System. This quiz covers market focus, growth factors, and system development lifecycle (SDLC) activities relevant to RMO. Understand the project team's assembly and feasibility analysis within the context of RMO's operations.