SDLC - Requirement Analysis For your course project you will specify the requirements. In this assignment you will produce the first deliverable for your course project, the requirements specification. The purpose of this assignment is for you to learn how to write a complete and precise requirements specification, which is the first step in developing a large software system. The teaching assistant is your customer, and he would like you to build a text editing system with the following features: Text Editing System A software system is desired for creating, storing, retrieving and modifying files of text. The text editing system will be accessible through a full-screen interface for interactive editing. The system will support a variety of editing commands, including inserting and deleting lines, modifying text in existing lines, and searching for text. You as the supplier are responsible for building a software system that meets the needs of your customer. However, they have given you a very ambiguous description of the system they want you to build. You must interview your customers and have them elaborate on the kind of system they want you to build. You must then write a requirements specification that resolves the ambiguities and precisely describes what will be the capabilities of the text editing system you build. Your requirements specification should specify the criteria that will be used to evaluate whether or not the final product meets the requirements. It should be concise, but with sufficient detail to resolve any potential misunderstanding between you and the customer. It should not specify implementation details, such as the data structures and algorithms you will use to implement the system; your customer is more concerned with what the system does, not how it does it. REQUIREMENTS DOCUMENT STRUCTURE Your document should have the following structure: A. A short introduction. Describe the situations in which the software will be used. How will the situation change as a result of introducing the software system? B. Functional requirements ("features/services"). C. Non-functional requirements ("constrains"). D. Represent a high-level diagrammatic description of the system, showing how the different functions provided by the system interact with each other. (use case diagram with description, class diagram, and sequence diagram) E. Discuss how did you deal with the customers while you were extracting the requirements.
SDLC - Requirement Analysis
For your course project you will specify the requirements. In this assignment you will produce the first deliverable for your course project, the requirements specification.
The purpose of this assignment is for you to learn how to write a complete and precise requirements specification, which is the first step in developing a large software system.
The teaching assistant is your customer, and he would like you to build a text editing system with the following features:
Text Editing System
A software system is desired for creating, storing, retrieving and modifying files of text.
The text editing system will be accessible through a full-screen interface for interactive editing.
The system will support a variety of editing commands, including inserting and deleting lines, modifying text in existing lines, and searching for text.
You as the supplier are responsible for building a software system that meets the needs of your customer. However, they have given you a very ambiguous description of the system they want you to build.
You must interview your customers and have them elaborate on the kind of system they want you to build. You must then write a requirements specification that resolves the ambiguities and precisely describes what will be the capabilities of the text editing system you build.
Your requirements specification should specify the criteria that will be used to evaluate whether or not the final product meets the requirements.
It should be concise, but with sufficient detail to resolve any potential misunderstanding between you and the customer. It should not specify implementation details, such as the data structures and
REQUIREMENTS DOCUMENT STRUCTURE
Your document should have the following structure:
A. A short introduction. Describe the situations in which the software will be used. How will the situation change as a result of introducing the software system?
B. Functional requirements ("features/services").
C. Non-functional requirements ("constrains").
D. Represent a high-level diagrammatic description of the system, showing how the different functions provided by the system interact with each other. (use case diagram with description, class diagram, and sequence diagram)
E. Discuss how did you deal with the customers while you were extracting the requirements.
Step by step
Solved in 3 steps
