Requirements Gathering and Analysis
The purposes of the Requirements Gathering and Analysis stage are:
• To establish and maintain agreement with the customers and other stakeholders on
what the system should do;
• To provide system developers with a better understanding of the system
requirements;
• To define the boundaries of (delimit) the system;
• To provide a basis for planning the technical contents of iterations;
• To provide a basis of finalizing cost and time to develop the system; and
• To define a user-interface for the system, focusing on the needs and goals of the
users.
During this stage the User Requirements Document (URD) providing high-level requirements
definitions and possibly basic architectural concepts is developed. The User Requirements
Document serves as a communication medium as well as a contract between the customer,
the users, and the system developers on the functionality of the system, which allows:
• Customers and users to validate that the system will become what they expected
• System developers to build what is expected
Design and Prototyping
The purposes of Design and Prototyping are:
1. To transform the requirements into a design of the system-to-be;
2. To evolve a robust architecture for the system; and
3. To adapt the design to match the implementation environment, designing it for
performance.
During the Design and Prototyping stage the following artifacts are created:
• Software Requirements Document (SRD) which list the system functionality;
• Architectural Design that specifies the solution architecture;
• Functional Design that contains the formalized functional and non‐functional
requirements; and
• For systems that interacts with end users a User Interface Prototype may be
developed.
Development and Unit Testing
During this stage the implementation details are specified and the system code is developed
and unit testing performed. The code is stored under version control system. Code reviews
shall also be conducted, in order to ensure code quality and its conformance to the coding
standards regular code reviews are conducted. Intermediate versions of the system may be
delivered to the customer for functionality review.
As a result the following artifacts are delivered:
Implementation Design that defines the solution’s implementation details; and
A fully functional version of the system that contains all the capabilities to be
provided in the final product.
Quality Assurance Process
Blumango is devoted to provide high quality solutions for its customers. To achieve this goal, we
have established a formal multistage quality assurance process. The process consist the
following main steps:
• Deep analysis of the project to understand all crucial points;
• Development of a right quality assurance strategy;
• Establishment of effective project processes;
• Automation of suitable activities (assessed during project analysis stage);
• Performance (scalability, reliability) evaluation; and
• Guaranteed result as output.
Usually, our approach is unique and varies for each specific project. However, our clients
can be sure that quality is top priority for us and given utmost importance.
Software Development Model Adopted by Blumango
Labels:
Process
Subscribe to:
Post Comments (Atom)
For more details, feel free to contact Armil(Marketing Manager):
Email : armil.velos@yahoo.com
Telefax : +63 32 416-0031
Mobile : 0927-309-8893
YM ID : incarmvel
BOOKMARK US
No comments:
Post a Comment