| |
|
| Scorpus
Delivery Model |
|
|
|
|
|
|
Scorpus
Enterprise Software Asset Management (ESAM)’ is provided
as a complete package, by structuring the product as required
for the software organization. This helps the customers
adapt and institutionalize the solution across the organization
covering multiple domains, departments or program stages.
The composition includes the base product licensed as per
the number of user in the organization. This is sufficient
to begin the initiate the software asset creation and consumption
program. This includes the client license + the portal.
The users can be administrators, creators, qualifiers and
consumers. |
|
If
one requires a automated asset creation and consumption capability,
then the composition can include the asset harvester, interfaces
to software development and management tools, workflow engine,
asset profiler, etc.
For the base product to fit into the organization’s
design time environment (i.e. application development and
maintenance), Scorpus team will either provide the integration
components or custom build one if it is specific to the customers
environment. Scorpus has few components readily available
for the implementation team to use during the adaptation phase.
Further to help the organization to initiate and continue
the software asset creation and consumption program, Scorpus
team provides consulting and adaptation services, which will
be a joint effort by the Scorpus + the client team members.
The engagement could last anywhere between 2-4 months based
on the scope and depth of the pilot taken up.
Jointly the team will set the objectives derived from the
organization goals. Based on the objectives the measures of
the program, direction and strategy is chosen and executed
within the defined period.
If there are multiple engagements to be managed, Scorpus team
can help ramp up the team size to run more than one engagement.
The end deliverables will be: |
|
|
|
|
 |
A
Set of software assets in the repository
Training on the software asset creation and reuse domain.
Program structure for the organization to follow and scale
the program.
Best practices and methodology.
Program measures, roles and the structure.
Integration of the repository with the design time environment
covering the requirements management, design, development
environment, testing tools and also with the version control
and management tools. |
|
|
|
|
|
|
|
|
|
| |
|
|
