|
| |
|
| |
TecnoAp has adopted RUP (Rational Unified Process) as Software Development Methodology. Our ISO-9001 quality procedures apply this methodology to medium or big sized computing projects.
Our infrastructure consists of about twenty-five Operative and Management Procedures, apart from forms and records which provide the software developments with a method, procedure and assurance quality framework.
It is for this that we have categorized each computing project as small, medium or big, according to the development effort, duration, number of people involved, etc. Therefore, a subset of procedures and records, adjusted to the project size, is determined, keeping the adequate equilibrium between methodology, documentation and project implementation.
|
|
| |
Brief description of the model
RUP methodology is a software Engineering generic process, which directs the cycle of life of the object oriented software development.
It describes a family of related processes and software engineering, which shares the same structure –i.e. ordinary process architecture. It also determines a task and responsibility assignment, adjusted to the project organization.
The aim of this methodology is to guarantee the high quality software production fulfilling final users´ needs within a well-defined schedule and budget. RUP embraces several of the best practices in the modern software development, being thus applicable to a wide range of projects and organizations.
 The best practices:
Some of the best RUP software development practices:
|
|
Incremental and iterative Development
It consists on dividing the software development cycle of life into several iterations. Each iteration possesses a series of activities, such as requirements management, analysis and design, implementation, testing and deployment. The development is carried out in an increasing way. Therefore, in the early stages of the development cycle of life, there exist “releases” of limited function, over which the “testing” and even the requirements and specifications validation with users are done. |
Project driven by use cases
The requirement administration is a systematic approach to find, document, organize and follow the changes in the system’s requirements. Requirement is understood as a condition or capacity which the system must fulfil. RUP methodology utilizes the Use Cases to define the system’s behaviour. Thus, the use cases which define the system are the bases of the entire development process. Within the project management, the use cases are utilized for the iterative development planning. |
Component architecture use
A component is a software non-trivial part, a module, a package, or a subsystem which fulfils a clear-cut function. It has a well-defined limit and can be integrated into a concrete architecture. The iterative development makes it possible for the components to be progressively identified and also allows us to decide on which ones to develop, purchase and reuse. During the analysis and design the components are organized into packages, subsystems and layers and their interfaces are determined. |
Visual Modelling
The use of a notation such as UML, semantically rich, graphic and textual to capture the software design, makes it possible to achieve an adequate abstraction level, also keeping the semantics and syntax accuracy. In this way, communication is improved in the development team while an unambiguous implementation basis is provided. |
Continuous quality verification
It is important that all the “artefacts” quality is kept in the project cycle of life during its development. Artefacts must be evaluated while the activities producing them are being completed and at the end of each iteration. Testing in each iteration guarantees the quality of the software being developed, since it permits the early elimination of any architecture error. Quality administration is implemented on every discipline, phases and iterations of RUP. |
|
|
|
|
|
