Free estimate on all our services

Welcome to Abe IT Consulting

Aligning technology to meet your business needs!

Special: Web site design, let's talk!

Abe IT Main

IT is 100% of what we do but only 10% of what they do

Read Abe response to IT questionnaires

7 Reasons why projects fail

Related Links:

Electronic Medical Record Open EMR

Free web templates

ExcelUser, Inc

Email us : info@abeitconsulting

Phone: 614-562-8471


Requirement Engineering

Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or users.
Requirements analysis is critical to the success of a development project Requirements must be documented, actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design. Requirements can be functional and non-functional.
Brainstorming and Theory Z principles based requirements analysis: A very early work identifying the whole field of requirements analysis was done by Moshe Telem of Tel-Aviv University in 1984-5. He published his work in 1987-8. Telem developed (and successfully implemented) a brainstorming and theory Z principles based requirements analysis approach, which he named Brainstorming a Collective Decision-Making Approach (BCDA), and technique (BCDT) for rapid, maximal and attainable requirements analysis through joint application design (JAD) - See JAD entry.

Requirements engineering
Systematic requirements analysis is also known as requirements engineering. It is sometimes referred to loosely by names such as requirements gathering, requirements capture, or requirements specification. The term requirements analysis can also be applied specifically to the analysis proper, as opposed to elicitation or documentation of the requirements, for instance. Requirements Engineering can be divided into discrete chronological steps:
• Requirements elicitation,
• Requirements analysis and negotiation,
• Requirements specification,
• System modeling,
• Requirements validation,
• Requirements management.
Requirement engineering according to Laplante (2007) is "a subdiscipline of systems engineering and software engineering that is concerned with determining the goals, functions, and constraints of hardware and software systems."In some life cycle models, the requirement engineering process begins with a feasibility study activity, which leads to a feasibility report. If the feasibility study suggests that the product should be developed, then requirement analysis can begin. If requirement analysis precedes feasibility studies, which may foster outside the box thinking, then feasibility should be determined before requirements are finalized.

Information gathered by Abe IT Consulting


Address: 5993 Brookmont Dr , Columbus OH 43026

2010 Abe IT Consultings

HomeBusiness Process AnalysisRequirement EngineeringSoftware DevelopmentTechnology