We engineer software. Other just craft it

Introduction & features

Business Modeling

System Specification

System Analysis & Design

Functional Testing

Roles in Software Development

ProClaris Practical Process™ overview

The ProClaris Practical Process™ represents the fer de lance of ProClaris. It is a lightweight version of the Rational Unified Process© (RUP©). Its strength relies on its practicality and applicability. Even though it can be used with any underlying technology, it has been optimized for the Microsoft .NET© framework.

In the following sections, a brief overview is offered for you to discover its principles.

All schemas have been produced with Rational XDE™.

The ProClaris Practical Process™ is covered in detail in a book authored by Enricos Manassis.

Introduction & features

Like any process the ProClaris Practical Process™ specifies the following elements:

• Who does an activity. A number of roles exist for each activity of the Process, e.g. Object Designer, Use Case Designer, Developer, etc.
•  
• How is the activity to be done. This is specified in terms of the output to be realized, e.g. Design an object, Design a Use Case, etc.
•  
• What is to be produced. This is referred as Artifact, e.g. Object Design, Use case Design. A subset of these will represent the actual deliverables of the project.
•  
• When is the activity to be done. The activities must be performed in a meaningful sequence, which is specified by the Process' Workflow of Activities.

The ProClaris Practical Process™ has an end-to-end comprehensive coverage of all the functional aspects of Software Development.

It is development centric, iterative and interactive. It makes a practical use of methods (Object Oriented Analysis & Design - OOAD), techniques and tools (Visual Studio© .NET, JBuilder©, Rational XDE™). A strong added value is also the traceability foreseen, through methods or techniques, i.e. the possibility to trace the consistency of any bit of code or any model up to the models or even specifications they derive from.

The applicability of the Process starts around 360 man days (that is 6 months for 3 persons), and has a median applicability of 2400 man days (6 months for 20 persons).

There are four main steps in the process:

1. Business Modeling
2. System specification
3. System Analysis & Design
4. Functional Testing

In the following sections you will get an inside look at the main process activities within each of the main steps mentioned above, which relate to the artifacts produced by each of these steps.

Page 1 of 6

<< 1 2 3 4 5 6 >>

© softclarITy 2010 All rights reserved. Privacy | Legal