Access Millions of academic & study documents

Software Requirements Elicitation

Content type
User Generated
Subject
Computer Science
Type
Homework
Showing Page:
1/8
Running head: SOFTWARE REQUIREMENT ELICITATION 1
Software Requirements Elicitation

Sign up to view the full document!

lock_open Sign Up
Showing Page:
2/8
SOFTWARE REQUIREMENT ELICITATION 2
Introduction
The successful development of software involves a series of specifications that entail
elicitation of requirements. Software requirements are the functionalities and features of a
particular target system. Ideally, elements reflect the expectation of users from the software
product being developed. Software Requirements Specifications (SRS) can be classified as both
known or unknown, and visible or hidden from the customer’s point of view. These foundation
pillars of a software essentially aid in development, user experience, driving design, and
supporting documentation. (Chung, 2012) Requirement Engineering is the process of gathering
software requirements, analyzing and documenting them. This paper examines the concept of
Software Requirement Elicitation.
Preparation of Requirement Kick-off Meeting
A kick-off meeting is an essential tool used in the communication of project specifications
to the stakeholders. It usually takes place after the project planning phase and just before the
implementation of the project. This meeting is attended by all the relevant project team as it marks
the official start of the project. The project team is informed of the project objectives and the level
of commitment required to meet the specified goals. A kick-off meeting facilitates a successful
project initiation and provides an additional boost of the motivation of the team member
(Chakraborty, 2010). Proper management of the kick-off meeting prevents the risk of obstruction
and allows the team to complete the project successfully.
A successful kick-off meeting involves some technical preparations in an attempt to
minimize project development obstruction. Preparation of the kickoff meeting consists of the
development of project goals and deliverables. These elements can be documented and the

Sign up to view the full document!

lock_open Sign Up
Showing Page:
3/8

Sign up to view the full document!

lock_open Sign Up
End of Preview - Want to read all 8 pages?
Access Now
Unformatted Attachment Preview
Running head: SOFTWARE REQUIREMENT ELICITATION Software Requirements Elicitation 1 SOFTWARE REQUIREMENT ELICITATION 2 Introduction The successful development of software involves a series of specifications that entail elicitation of requirements. Software requirements are the functionalities and features of a particular target system. Ideally, elements reflect the expectation of users from the software product being developed. Software Requirements Specifications (SRS) can be classified as both known or unknown, and visible or hidden from the customer’s point of view. These foundation pillars of a software essentially aid in development, user experience, driving design, and supporting documentation. (Chung, 2012) Requirement Engineering is the process of gathering software requirements, analyzing and documenting them. This paper examines the concept of Software Requirement Elicitation. Preparation of Requirement Kick-off Meeting A kick-off meeting is an essential tool used in the communication of project specifications to the stakeholders. It usually takes place after the project planning phase and just before the implementation of the project. This meeting is attended by all the relevant project team as it marks the official start of the project. The project team is informed of the project objectives and the level of commitment required to meet the specified goals. A kick-off meeting facilitates a successful project initiation and provides an additional boost of the ...
Purchase document to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.
Studypool
4.7
Indeed
4.5
Sitejabber
4.4

Similar Documents