Requirements Management Practice Description
1.
REQUIREMENTS MANAGEMENT (RM)
1.1
Description of the practice
TRASYS provide solutions to effectively manage critical issues and reduce risks in project related to unavoidable requirements changes or business changes. This practice is concerned with producing and managing a set of specifications throughout the entire Software development lifecycle (SDLC) according to the stakeholders needs.
1.2
Services offering
TRASYS consultants deliver services in the fields of requirements definition, requirements management, as well as business and functional analysis.
Examples of the services covered by the practice are:
Requirements Elicitation, Analysis & Specification.
TRASYS has a strong experience in the field of requirements engineering. Based on our experience in this area, we have developed a methodology based on best practices in the field and concrete experiences. It includes the following activities:
o The project context, scope and constraints are defined at high level during a first meeting with the stakeholders.
o During the elicitation phase the requirements are identified, analyzed and prioritized and conflicts between requirements are managed.
o The writing activity is in charge of producing the resulting Software Requirements Specification (SRS) with a high quality level.
o The quality assurance is in charge during the whole process of evaluating and improving the quality of the specifications.
Practice Description Requirements Management
Requirements Management. Our approach is not only listing and detailing the requirements of the
information system, but also to deal with risks, requirements prioritization, requirements change, and requirements traceability throughout the whole lifecycle of a development project. Because we know that requirements change frequently, TRASYS puts in place a streamlined but flexible policy governing the requirements change with the objective to avoid scope creep.
Development methodology support. As “Requirement” is a key discipline of development methodologies like
RUP (and more agile methodology like OpenUP), TRASYS developed best practices to support the customer optimizing the work of this discipline, part of the chosen development methodology.
Considering for instance the RUP methodology, work towards achieving the Requirements’ discipline goal is centered on the following activities:
o Development of technical vision which comprises the preliminary analysis of the system scope;
o Identification and refinement of requirements throughout the project execution. It includes the
gathering, modeling and analysis of the requirements as well as their ongoing management.
Requirements elicitation Writing requirements Quality assurance Validation Project context and constraints
Practice Description Requirements Management
An overview of the RUP Requirement discipline’s activities is shown in the following figure:
1.3
Best practices & Technologies
TRASYS ensures that requirements are defined, managed and dealt accurately by using best practices and technologies, frameworks and tools in the domain of Requirements Management such as:
RUP (Rational Unified Process by IBM). A comprehensive process framework with best practices that provides guidelines, templates, and examples for software development implementation, which is intended to be adaptable and customized for specific organizations and their projects.
OpenUP. An agile and Unified Process that contains the minimal set of practices to develop software.
UML (Unified Modeling Language). A standardized modeling-language aiming at specifying, visualizing and
document an abstract model of software systems, including their structure and design, as well as representing organizational structures.
IEEE 1016 / 830 standards: They related with the Software Design Description and Software Requirements
Specification, aiming to describe the content and qualities of a good requirements specifications and software design.
CMMi (Capability Maturity Model Integrated). It is a set of practices for process improvements that includes
eliciting and managing requirements, decision making, measuring performance, planning work, and handling risks, among other topics.
SCRUM (Agile): an iterative, incremental framework for the management of software development.
O n g o in g m a n a g e m e n t
Practice Description Requirements Management
TRASYS consultants have expertise with the following modeling software:Rational Software Architect Rational RequisitePro Enterprise Architect Borland Together StarUML
1.3.1
Professional qualifications
TRASYS consultants are knowledgeable in several internationally recognized frameworks used for achieving requirement and service management such as:
OCUP (OMG Certified UML Professional); OCEB (OMG Certified Expert in BPM);
CPRE (IREB Certified Professional for Requirements Engineering); RUP (IBM Certified Solution Designer).
1.4
Key references
TRASYS consultants have achieved successful projects for the following clients:
• Customer case 1:
o Client:
A public sector organisation
o Challenge:
To write the specifications for a Request for Proposal (RFP) for a new IT solution for the construction sector in Wallonia.
o Our solution:
We defined the methodology and the template for writing RFP. TRASYS collected the requirements, perform a market study of the existing solutions and model the future business processes & requirements using the Enterprise Architect tool.
• Customer case 2:
o Client:
An international steel company
o Challenge:
The IT department of our client was facing a problem of weakness of the business and functional specifications issued and wished to address it through the review of the related process and templates and training courses aimed at both business users and IT staff.
o Our solution:
The review of the process and responsibilities associated with the production and processing of the IT requests and of the business and functional specifications.
The definition of new templates for the specifications.
The training of the business and IT staff (100 people in France and Belgium) on writing specifications.
Practice Description Requirements Management
• Customer case 3:
o Client:
An international public sector office
o Challenge:
Our client needed support in writing an RFP for the procurement of a new Information and Reporting System and in coaching them through the procurement cycle.
o Our solution:
We defined and specified the procurement procedure, the ICT system needs (business processes, use cases, requirements) and the support needs, such as hosting requirements and SLAs as well as the project management and governance needs. The methodologies used by TRASYS include ITIL V3, COBIT V4.1, CMMi, RUP and TOGAF.