title

Business process analisys

Business process analysis collects and gives a representation of workflows and every activity, aiming to show cost and timescale optimization opportunities, or to spot resource waste and inefficiencies.
The value of business process analysis resides in providing the customer documentation in the way in which its people work, and highlights times and costs of each processing stage.

Tools used:
BPMN, BPEL, Catalyst, IDEF-0, Flow chart, text documents and spreadsheets

Requirement analysis

The initial stage of the software lifecycle aims to draw, describe and catalog business requests, with the aim of documenting the requirements and relevant reciprocal relationships and dependencies. The requirements analysis determine the outcome of the project, so it usually is (or should be) subject to formal approval by the stakeholders.The requirements analysis drives the subsequent functional specification stage and planning of validation activities.

The requirements analysis drives the subsequent functional specification stage and planning of validation activities.
The value provided refers to show to have taken into account every aspect of the needs expressed by the client

Tools used:
UML [UCD], OSRMT, text documents and spreadsheets

Function analysis

The Function Analysis deepens or (in small, simple projects) replaces, le requirement analysis. The main target of this phase is to detail the required system behaviors and user experience. A function analysis consists of the collection required of functionalities description and adds project and architecture dependent constraints.

The value refers to the transformation of a requirements collection to a non-overlapping functions, ready for the subsequent design stages.

Tools used:
UML [UCD, OSD, CD, AD], ArgoUML, Rational Software Architect, text documents and spreadsheets

System design

The Design can either be feed by the functional analysis or, in case of reverse engineering, directly be the code under translation. The Design activity aims to describe at the deepest possible detail level the required functionalities and behaviours.

The value offered is tightly related to the final quality of the designed technical products; moreover the design documentation is the reference for subsequent system evolution and maintenance.

Tools used:
UML [OSD, Coll, Act, Dep], ArgoUML, Rational Software Architect, text documents and spreadsheets

Solution architecture

A software system can be viewed like a complex structure of interrelated architectural elements. Working to the solution architecture means defining the macro components to be used or to be built that interact together and the relevant working parameters like throughput, performances, dislocation, service delivered, applied performance indicators, and anything that could contribute to the system definition, from a structural point of view.

The value provided is a formal description of the system architecture, precious for operation teams and for the development groups.

Tools used:
UML [Dep], ArgoUML, Rational Software Architect, text documents and spreadsheets

Service management

The business service management consists of the operating activities of the systems, specifically:
– User enablement Management
– Performance monitoring
– Detecting and addressing issues
– Service request management
– Interaction with the support and the service desk teams
– Reporting on trends
– Updating systems
– Reporting on activities
– Process Management

The value of service management in a nutshell is the guarantee that the system deliver the required service in the right way.

Tools used:
ITIL, MS-Office, Trouble ticket systems, MS-Project, resource planning

Supervision / team leading

The supervision and team leading is to receive and distribute requests for processing in a group, and monitor the operating parameters of the group, such as schedules, performance, compliance with deadlines, critical.
This role ensures the production of the various “working package” entrusted, periodic reporting on progresses and escalation of issues.
The value for this activity is that the tasks assigned are effectively executed as required.

Tools used:
MS-project

Project management

A project is a set of activities to ensure value delivery compared to the resources received in staging to reach a certain goal.

A project implies change, is temporary, is cross-functional, is unique and uncertain. The project management deals with these constraints covering the planning, delegation, monitoring and control of every aspects; another target for a project manager is the motivation of the people involved in order to achieve the project objectives within a system of constraints on time, cost, quality, scopes, risks and benefits.
The value provided is ensuring, within a system of agreed tolerances, that the targets for time, cost, quality, scope, risks and benefits are reached.

Tools used:
MS-project, PRINCE2, the project teams

Program management

A program is a set of projects, managing a program means to monitor and coordinadinate the progresses of the various projects within a budget constraint and predetermined times. The value of the role of program management is primarily concerned with ensuring that the business need are fulfilled in the the answered direction.

Tools used:
MS-project

Test leading

A test leader has the responsibility to collect and document functional and architectural requirements and on that basis to set the testing strategy which will be followed in test planning phases.
In addition the test leader collects data feeds of the activities assigned to his team and addresses the setup of the test environments.

The value provided is the certainty of a coordination between the activities and the guarantee of product quality according to the requirements and within agreed tolerances.

Tools used:
Quality assurance specific tools like HP-QC, HP-ALM, ANT, IBM Quality Manager