Reference no: EM133991362

Project - Software Requirements Specification

Mission:
Your company ABX has been commissioned by a customer to create a stand-alone Personal Computer based GUI software system for the Word Processing.

Your manager has given you the mission to draw up the requirements document to be presented and approved by the customer. Your manager will review the document before it is presented to the customer to check for completeness, accuracy, and clarity. You have been given the specification template that your team has used successfully in the past (project1-specification-template.docx). You must use this template and fill out all appropriate sections.

The manager has given you a document describing the customer's needs for the system (ABX-WordProcessing-Customer-Guidelines.docx) that you will use for your requirements. This document is the result of interviews with the customer to gather his wants and needs.

The objective of this project is to apply and practice writing up requirements based on the customer's needs and wants. You cannot change what the customer is asking for but you can add additional details that may be needed for a complete system. In fact you may have to add some details that may be implied by existing requirements or are needed to make the system fully functional (e.g. define the non-functional requirements). System functionality and the flow of the program must be as given by the customer. You need to divide the requirements into logical features and describe fully using the stimulus/response format for your requirements. No AI shortcuts - Just Genuine Assignment Help from Real Tutors.

It is expected that once the specifications have been approved by the customer, another team will design and implement the system. You will not be designing or implementing this program. Your document must not change any of customer's requirements and must be as complete as possible to design and implement the system without going back to the customer or the document describing customer's needs. You should not be adding any new features that customer did not specify.

Introduction (purpose, intended audience, product scope, references)
Overall description (product functions, user characteristics, operating environment, user documentation)
Constraints on the software system, assumptions, and dependencies
User interfaces overview and the basic flow of the system from the external/user view
System requirements - complete set of functional requirements describing all the features and functionality of the system (using stimulus/response format)
Non-functional requirements the system should have (you will make these up based on what you learned about non-functional requirements and the needs of this type of program)