Scribd
Upload
55 views7 pages

Assignment 1

This document is an assignment submission for a software requirements engineering course. It was submitted by Mujahid Hussain to his professor Mr. Fazal Wahab. The assignment discusses key topics in requirements engineering including requirements elicitation and documentation, requirement types such as functional, quality, and constraints. It also covers characteristics of requirements engineers and concludes by emphasizing that requirements define what the system should do and constrain its development and implementation.

Uploaded by

Mubasher Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
55 views7 pages

Assignment 1

This document is an assignment submission for a software requirements engineering course. It was submitted by Mujahid Hussain to his professor Mr. Fazal Wahab. The assignment discusses key topics in requirements engineering including requirements elicitation and documentation, requirement types such as functional, quality, and constraints. It also covers characteristics of requirements engineers and concludes by emphasizing that requirements define what the system should do and constrain its development and implementation.

Uploaded by

Mubasher Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Assignment # 1

Submitted By:Mujahid Hussain


Submitted To: Mr Fazal Wahab
Registration No: 1737
Subject:Software Requirements Engineering
Program: MS (CS)
Date of Submission: 06-10-2018

Abasyn University Islamabad


Software Requirements Engineering
Introduction:
The software requirements are description of features and
functionalities of the target system. Requirements convey the
expectations of users from the software product. The requirements can
be obvious or hidden, known or unknown, expected or unexpected
from client’s point of view.

The process to gather the software requirements from


client, analyze and document them is known as requirement
engineering. The goal of requirement engineering is to develop and
maintain sophisticated and descriptive ‘System Requirements
Specification’ document.

Review:
Software engineering is an engineering branch associated
with development of software product using well-defined scientific
principles, methods and procedures. The outcome of software
engineering is an efficient and reliable software product.

Software design is a process to conceptualize the software


requirements into software implementation. Software design takes the
user requirements as challenges and tries to find optimum solution.
While the software is being conceptualized, a plan is chalked out to
find the best possible design for implementing the intended solution.

Software project management has wider scope than


software engineering process as it involves communication, pre and
post delivery support etc.

In this chapter “Requirements Engineering”, first topic is


about Requirements. A requirement is basically, A condition or
capability needed by user to solve a problem or achieve an objective or
a capability that must be met or possessed by a system or system
components to satisfy a contract, standard, specification, or other
formally imposed documents. During collecting requirements a
software engineer must care about Stakeholder needs.

Goal of requirements engineering during the development


process, requirements engineering must elicit the stakeholders
requirements, document the requirements in a suitable manner,
Validate and verify the requirements and manage the requirements
over the course of the entire life cycle of the system

Requirements engineering is a systematic and disciplined


approach to the specification and management of requirements with
the following goals

• Relevant Knowledge
• Understanding and Documenting

On the other hand the Core activities of requirements


engineering is:

• Elicitation

• Documentation

• Validation

• Negotiation

A requirement needs to meet several criteria to be considered a “good


requirement”

Characteristics of a Requirements Engineer

• Analytic thinking

• Empathy

• Communication skills

• Conflict resolution skills

• Moderation skills

• Self-confidence

• Persuasiveness
Requirement Types

There are three basic types of requirements

• Functional Requirement

• Quality Requirement

• Constraint

Functional Requirement:

• Statements of services that the system should provide, how


the system should react to particular inputs and how the
system should behave in particular situation.

• Depend on the type of software, expected users and the


type of system where the software is used.

• Functional user requirements may be high-level statements


of what the system should do; functional system
requirements should describe the system services in detail

Quality Requirement:
A quality requirement is a requirement that pertains to a quality
concern that is not covered by functional requirements.

Constraint:
A constraint is a requirement that limits the solution space
beyond what is necessary for meeting the given functional
requirements and quality requirements

Categorization of Quality Requirements:


• Performance of the system

• Security of the system

• Reliability of functionalities

• Usability of a system

• Maintainability of a system

• Portability of a system

Conclusion:

Requirements set out what the system should do and define


constraints on its operation and implementation. Functional
requirements set out services that the system should provide. Non-
functional requirements constrain the system being developed or the
development process. User requirements are high-level statements of
what the system should do.

User requirements should be written using natural language,


tables and diagrams. System requirements are intended to
communicate the functions that the system should provide. System
requirements may be written in structured natural language. A
software requirements document is an agreed statement of the system
requirement

References:

http://www.inf.ed.ac.uk

www.ou.nl

www.tutorialspoint.com

www.oreilly.com

You might also like