ACS2913 Software Requirements Analysis

Software Requirements Analysis and Design

• Course: ACS2913
• Instructor: David Tenjo
• Gathering and documenting requirements is crucial for software development.
• Specificity and clarity in information gathering are essential.
• Methods (techniques) for gathering good information about the system are needed
• A good analyst gathers specific, detailed, and relevant requirements.
• Documentation is vital for systems designers and developers.

How to Identify Requirements

• Information gathering is also known as "information Gathering".
• Clear, detailed, and accurate information is vital in defining a system.
• Specific methods (techniques) facilitate the process.

Information Gathering Techniques

• Interviewing users and stakeholders is a technique
• Distributing and collecting questionnaires helps gather user input.
• Review of inputs, outputs, documentation and other supporting documents is an important part of the process.
• Observing and documenting business procedures provide essential details
• Researching vendor solutions to understand similar systems is helpful.
• Collecting active user comments and suggestions is important
• Following up when necessary is key to completing information gathering tasks

Interviewing Users and Stakeholders

• Detailed questions must be developed and prepared.
• Meetings with individuals or groups of users are important to gather information from the desired individuals.
• Document answers from the interviews
• Follow-up interviews and meetings, if necessary, are required to answer all questions

Themes and Questions

• Themes identify potential areas for information gathering
• Questions to users are developed from the themes and help identify needed information.
• Themes and questions help users identify the needed information.

Preparing for the Interview

• Establish the interview's objective.
• Identify appropriate users, and project team members.
• List questions and issues.
• Review relevant documents.
• Set the time and location of the meeting.
• Inform all participants of the purpose, time, and location.

Checklist for Interviewing (Before, During, After)

• Before: Establish objective, determine correct users, decide who participates, build a list of questions, review related documents/materials, and set time/location.
• During: Arrive on time, look for exceptions/errors, clarify details, note everything in a thorough manner, document unanswered items/questions.
• After: Review notes accurately and completely, transfer information to appropriate models and documents, clarify any needed issues, thank everyone, follow up.

Interview Session Agenda

• Example agenda includes specifics about participants, objective, date, time, place, specific discussion items(example: who is eligible for commissions?)

Keeping an Open Items List

• A list of open items with specifics about who is responsible to address the issues.
• Dates for the issues is to be addressed

Distributing and Collecting Questionnaires

• Questionnaires are tools to gather information from multiple stakeholders.
• Example questionnaires are provided concerning customer support system.

Review Inputs, Outputs, and Procedures

• Comprehensive analysis of forms, processes, and procedures is needed

Additional Techniques

• Observe and document business processes.
• Research vendor solutions
• Collect active user comments and suggestions.

Defining Requirements

• Defining requirements is performed after information gathering.
• Multiple methods can be used to define requirements.

Models and Modeling

• Models are representations of system aspects.
• Different model types include textual, graphical, and mathematical ones.
• Examples of model types include: UML models (use case, class, sequence, communication, state machine, activity diagrams).

Reasons for Modeling

• Models assist in simplifying complexity, communicating details to different stakeholders.
• Models document decisions needed.
• Models help maintain and enhance the system.

Analysis and Design Model Samples

• Various models (e.g., event list, use case diagram, sequence diagram, activity diagram, communication diagram, state machine diagram) visualize different system aspects.

Documenting Workflows with Activity Diagrams

• Activity diagrams show processing steps in a workflow
• Diagrams include the user's role, and sequences of activities

Activity Diagram Symbols

• Various symbols in activity diagrams signify beginning/end points, tasks, transitions, decision points, and more.

Activity Diagram for RMO Order Fulfillment

• Activity diagram showing a step-by-step process for handling RMO orders.

Activity Diagram with Concurrent Paths

• Illustrates workflows handled by multiple functions (e.g., sales, engineering, purchasing, production, scheduling).

Summary

• Techniques used in the project include information gathering (interviews, questionnaires, document review, observation).
• Model types such as Activity Diagrams are used.
• The Unified Modeling Language (UML) is a standard tool for modeling system aspects.

This quiz focuses on the essential techniques for gathering and documenting software requirements. It covers various methods for effective information gathering and highlights the importance of clarity and specificity in the process. Perfect for students looking to enhance their skills in software design and analysis.