 |
|
|
|
 |
|
|
|
Analysis & Design |
|
|
|
 |
|
|
|
|
The following documents are available for download:
• Creative Services Overview (105K, PDF )
Related Links:
• User Interface Design
|
|
|
|
|
|
7Studios leverages Unified Modeling Language(UML) By creating a package of models that
each add to the "picture" of the solution,
7Studios can help the client and its software engineers
reduce confusion over scope and expectation related
issues.
Conceptual Diagrams
As the first model document produced, the conceptual
diagram shows the relations between major systems,
their boundaries, and how they interact at a high level.
This diagram gives both the business user and the software
analysis analyst the ability to communicate about the
overall solution at a high level. This document
is then leveraged in building the actual components
and verifying completion of the system.
Use Case Diagrams (UCD)
The UCD describes the
functional elements of the system for all components
as well as also defining the appropriate security relationships
with the components, and the actual users of the system.
Use Case Scenarios (UCS)
As an extension of
the UCD, the UCS define the business processes for
each case, and becomes the manual test scripts for
the system to verify it is performing appropriately. Each
of these scenarios is outlined and used for system
development. The UCS provides "state" or
point-in-time references to pre-conditions, post-conditions
and failure/error handling for the system. The
UCS provides the narrative for when and how each function
of the application should perform.
Static Diagrams
Static Diagrams, sometimes known
as physical diagrams, are the representation of the
actual classes/objects that will be built as well as
the relationships between those classes. The Static
Diagram requires information from the previous diagrams
to accurately complete the picture of what will be
built. These models also show the business user the
fields that will be available for use on screen and
in reporting.
Sequencing Diagrams
As the final diagram, the sequencing
diagram exists to assist the software developer with
where parts of the application will run (client/server/database)
and what the logical sequence of actions are to support
all the features and functionality that the previous
documents have described as "the system".
Wire Frames
Conceptual visual presentation of the
User Interface (UI) that provides the user of the system
with interactive functionality defined in previous
design documents. Wire Frames are meant to convey
conceptually how the system user(s) will interact with
the system.
Technical Requirements
Those items in the functional
requirements that will need technical detail (ie. special
business rules, standards, technology platform configurations,
etc.) are outlined in a Technical Requirements document.
This structure is adapted to the project and grows
during the life cycle of the project. |
|
|
|
|
|
|
|
|
