Program
Specifications
And
User Requirements
COMPUTER PROGRAMMING 5
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Software and User Requirements: A Guide for Programming, Summaries of Computer science
A basic overview of software requirements specification (srs) and user requirements specification (urs) in the context of computer programming. It explains the purpose and content of these documents, highlighting the importance of defining functional and non-functional requirements. The document also explores common requirements elicitation techniques, such as interviews, observations, document analysis, and prototyping, which are essential for gathering user needs and translating them into actionable requirements.
Typology: Summaries
2022/2023
1 / 11
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Software and User Requirements: A Guide for Programming and more Summaries Computer science in PDF only on Docsity!
Program
Specifications
And
User Requirements
COMPUTER PROGRAMMING 5
Looping Statement Loop control statements change execution from its normal sequence. When execution leaves a scope, all automatic objects that were created in that scope are destroyed. Statements inside a loop are executed repeatedly provided with some condition which terminates the loop. For loop executes a set of statements repeatedly until a specified condition evaluates to false. while & do while โ Do while loop is similar to that of the while loop except that the condition is evaluated at the end of the loop in do-while whereas in while loop, it is evaluated before entering into the loop.
User Requirements Specification (URS) URS is generally a planning document, created when a business is planning on acquiring a system and is trying to determine specific needs.
The URS should include:
- (^) Introduction โ including the scope of the system, key objectives for the project, and the applicable regulatory concerns
- (^) Program Requirements โ the functions and workflow that the system must be able to perform
- (^) Data Requirements โ the type of information that a system must be able to process
- (^) Life Cycle Requirements โ including how the system will be maintain and users trained
Common Requirements Elicitation Techniques Asking users about their tasks-related problems, and how they want the software to assist them.
- (^) Interview transcript โ word-for-word written record of the entire interview.
- (^) Interview minutes โ are record of only the key points of the interview`
INTERVIEW
Common Requirements Elicitation Techniques Watching users carry out their tasks
OBSERVATIO
N
Common Requirements Elicitation Techniques Producing an early version of the software and asking users for feed back
- (^) Throwaway prototype โ preliminary version of the software, purpose is to help users visualize the software the he/she wants
- (^) Evolutionary prototype โ not thrown away but is continuously extended