digiploy Client Interaction Process

1
digiploy Client Interaction Process
2
Terms

• Business Use-Case Model
• The Business Use Case Model is a diagram
  illustrating the scope of the business being
  modeled. The diagram contains business users and
  the services or functions they are requesting
  from the provider.
• Business Use-Case
• A business use case specifies the desired kinds
  of interactions between a business/organization/fi
  rm and its clients
• Use-Case Model
• The Use Case Model is a diagram illustrating the
  scope of the application being built. The diagram
  contains users and the services or functions they
  request from the application.
• Use-Case
• A normal use case specifies the desired kinds of
  interactions between a computer system and its
  users.

Start
Business Modeling (Workflow)
Business Modeling (Activity)
Requirements
Construction
Transition
Finish
3
Business Modeling
The Purpose of the Business Modeling Discipline
is To understand the structure and the dynamics
of the organization in which a system is to be
deployed (the target organization) and to ensure
that customers, end users, and developers have a
common understanding of the target organization.
Start
Business Modeling Workflow At Digiploy
Business Modeling (Workflow)
Identify Business Processes Within the team we
need to come to a common understanding of what
the boundaries are of the organization we are
describing. Activity 1) Capture a common
business vocabulary To define a common
vocabulary that can be used in all textual
descriptions of the business, especially in
descriptions of business use cases. Activity 2)
Find Business Actors and Use Cases To outline
the processes in the business. To define who and
what will interact with the business. Refine
Business Process Definitions Next, each business
use case will be assigned an actor who is
responsible for describing it in detail. Acting
as business designer, that person will complete
the definition of the business use case and lead
a review session. The business designer may also
invite representatives or stakeholders to the
project, such as end users. Activity 1) Detail a
Business Use Case To describe the business use
case's workflow in detail. Activity 2) Review
the Business Use-Case Model To formally verify
that the results of business use-case modeling
conform to the stakeholders' views of the
business.
Business Modeling (Activity)
Requirements
Construction
Transition
Finish
4
Business Modeling
Start
Business Modeling (Workflow)
Business Modeling (Activity)
Requirements
Construction
Transition
Finish
5
Requirements

• The purpose of the Requirements discipline is
• 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 estimating time to develop
  the system.
• To define a user-interface for the system,
  focusing on the needs and goals of the users.

Start
Activities Involved For Requirements At Digiploy
Business Modeling (Workflow)

• Step 1) Capture a Common Vocabulary
• To define a common vocabulary that can be used in
  all textual descriptions of the system,
  especially in use-case descriptions.
• Step 2) Find Actors and Use-Cases
• To outline the functionality of the system.
• To define what will be handled by the system and
  what will be handled outside the system.
• To define who and what will interact with the
  system.
• Step 3) Develop Vision
• Define the boundaries of the system.
• Describe primary features of the system.

Business Modeling (Activity)
Requirements
Construction
Transition
Finish
6
Construction

• The purpose of construction is
• To define the organization of the code, in terms
  of implementation subsystems organized in layers,
  
• To implement classes and objects in terms of
  components (source files, binaries, executables,
  and others),
• To test the developed components as units, and
• To integrate the results produced by individual
  implementers (or teams), into an executable
  system.
• The Implementation discipline limits its scope to
  how individual classes are to be unit tested.
  System test and integration test are described in
  the Test discipline.

Start
Business Modeling (Workflow)
Business Modeling (Activity)
Requirements
Construction
Transition
Finish
7
Transition

• Objectives
• The focus of the Transition Phase is to ensure
  that software is available for its end users. The
  Transition Phase includes testing the product in
  preparation for release, and making minor
  adjustments based on user feedback.
•  
• Essential activities
• Training of users and maintainers
• Finalizing end-user support material
• Testing the deliverable product at the
  development site
• Creating a product release
• Getting user feedback
• Fine-tuning the product based on feedback
• Making the product available to end users

Start
Business Modeling (Workflow)
Business Modeling (Activity)
Requirements
Construction
Transition
Finish
8
In Closing
Any outsourced software project has a significant
amount of work that does not require direct
involvement or face-time with the client. Such
activities (coding, unit testing, documentation,
etc.) can be very effectively carried out in
cost-effective and high quality offshore delivery
centers. Our approach is built around balancing
onsite and offsite teams to reduce cost, speed
development cycles, and ensure the entire project
is handled in a professional manner.
Start
Business Modeling (Workflow)
Business Modeling (Activity)
Requirements
Construction
Transition
Finish
Created by digiplay designs