1. Software Development Case
The following sections outline a preliminary Software Development Case for the Indigent Defense On-Line (IDOL) system. The content of this development case will be confirmed, and the subject of formal signoff during IDOL Inception.
1.1. Introduction
Purpose
The purpose of a Development Case is to capture and describe the development process that will be used for a project. The process is based on the Rational Unified Process (RUP), which is a large and searchable knowledge base of best practices for software development projects.
This document reflects the portions of RUP that will or will not be used, including activities, roles and artifacts for the IDOL application. A standard Development Case for the Sierra Systems Software Development Center (SDC) has been defined and forms the foundation for the IDOL Development Case.
Scope
This Development Case encompasses the entire development process, regardless of whether the work is done at the Tarrant County site or at the SDC. The IDOL Development Case references the Software Development Center Development Case.
Definitions, Acronyms, and Abbreviations
The following terms are part of the language used in this Development Case document:
Table 1-1. Definitions, Acronyms, and Abbreviations
Acronym/Abbreviation / Term/Definition /RUP / Rational Unified Process
SDC / Software Development Center
PRA / Project Review Authority
SDP / Software Development Plan
ECFS / Electronic Case Filing System
IDOL / Indigent Defense On-Line
References
[RUP] Rational Unified Process, Rational Software
[ECFS SDP] ECFS Software Development Plan
[SDC DEVCS] Software Development Center, Development Case, Version 1.11
1.2. Overview of the Development Case
Lifecycle Model
A high level overview of the SDC lifecycle, which is based on the Rational Unified Process (RUP) is provided in the [SDC DEVCS].
The following table shows which disciplines, grouped as support and engineering will be exercised during the four phases of the RUP for the IDOL project:
Table4. 2-1. Support Disciplines
Discipline Name / Inception / Elaboration / Construction / Transition /Project Management / X / X / X / X
Configuration Management and Change Control / X / X / X / X
Environment / X / X / X / X
Table 4.2-2. Engineering Disciplines
Discipline Name / Inception / Elaboration / Construction / Transition /Business Modeling / - / - / - / -
Requirements / X / X / X / X
Analysis and Design / X / X / X / X
Implementation / - / X / X / X
Test / X / X / X / X
Deployment / - / X / X / X
Refer to the IDOL Software Development Plan for project schedule, resources, and other project specific information. Refer to the SDC Development Case for the baseline against which the IDOL Development Case is applied.
Disciplines
This Development Case document covers the following disciplines from RUP: Business Modeling, Requirements, Analysis & Design, Implementation, Deployment, Test, Configuration & Change Management, Environment and Project Management.
4.2.1 Discipline Configuration
The purpose of this section is to explain how the discipline configuration works. This includes an explanation of the purpose for various tables and other sections of the Development Case.
Workflow
In most instances the workflow detail steps defined in the [SDC DEVCS] are referenced. Only in instances where modifications to the workflow detail steps have been made, will the workflow detail step table be provided in this document. For each step, the RUP has activities and extensive support material. The workflow table does not duplicate this information. It is intended to assist the project team in understanding the essence of what needs to be done for each step.
Artifacts to Produce
The ‘Artifacts to Produce’ table is provided for each discipline to ensure a common understanding of the artifacts to be produced and the review level(s) associated with them. The following table explains the ‘Artifacts to Produce’ table:
Table 4.2-3. Explanation - Artifacts to Produce table
Column Name / Purpose / Contents/Comments /Artifacts / The name of the artifact. / A reference to the artifact in the Rational Unified Process or to a local artifact definition held as part of the development case.
Status / Qualify how the artifact is used across the lifecycle. / Decide for this phase:
• Initial : The document will not be finished in this iteration. This should be accompanied by an explanation of how far the artifact should be taken
• Update : The document was begun in a previous iteration and that one should be updated
• Final : The document will be finalized this iteration, and is unlikely to be changed.
• New : The artifact is considered brand new in each iteration. Even though previous versions of the artifact were created, they were completed and this will be a new effort.
Review Level / Define the review level, and review procedures to be applied to the artifact. / Decide review level:
• Formal-External
• Formal-Internal
• Peer-PRA
• Peer
• None
Artifacts Referenced from ECFS
The approach being taken for the IDOL application is to leverage investment made for ECFS. At each stage of the project, only those artifacts which have specific content change as the result of the IDOL work will be updated. The remaining artifacts will be referenced unchanged from ECFS.
Artifacts Removed and Rationale
Any artifacts that are not produced are listed and the rationale for the removal is defined.
4.2.2 Review Levels
This project uses the following review levels:
· Formal-External : The artifact will follow a formal review process not to assure quality, but rather to gain agreement from all parties. A formal review record will be produced to prove the review happened and to serve as a paper trail that external parties accepted the review.
· Formal-Internal : The artifact will follow a formal review process to improve its quality, and will have a formal review record to prove the review happened and to guide process improvement.
· Peer-PRA : This is a peer review, but the Project Review Authority is invited to attend, so there is a slightly higher degree of formality than a typical Peer review, but less than that of a Formal- Internal. In a more formal environment, a Formal-Internal review precedes Peer-PRA reviews.
· Peer : The artifact will be shared with peers to ensure quality, a formal review document will be produced.
· None : No review is expected for this artifact.
Refer to the [ECFS SDP] for the project specific review levels practices and procedures.
4.2.3 Tools Used
Refer to the [SDC DEVCS] for a detailed listing of the SDC tool set (this does not include a definition of the SDC development infrastructure).
1.3. Inception
This section defines the process that the Sierra Systems ECFS ProjectIDOL Project Team will follow during Inception. The IDOL work that will occur during this phase will update the existing artifacts produced during ECFS Inception to reflect the added functionality of IDOL.
4.3.1 Project Management
Workflow
Inception artifacts will be updated to reflect the addition of IDOL scope.
Artifacts to Produce
As per the [SDC DEVCS], the following artifacts will be produced:
Table 4.3-1. Project Management Artifacts to Produce
Artifacts / Status / Review Details /Iteration Plan (Inception) / New / Formal-External
Iteration Plan (Elaboration) / New / Formal-External
Iteration Assessment / New / Peer – PRA
Software Development Plan / New / Formal – External
Review Record / New. Many.
/ None
Risk List (in Primavera) / New / Peer - PRA
Issues List (in Primavera) / New / Peer - PRA
Work Order (WBS in Primavera) / New / None
Function Point Analysis (indicative) / New / Formal-External
Artifacts Referenced from ECFS
The following ECFS artifacts will remain unchanged .
Table 4.3-2. Project Management Artifacts Referenced from ECFS
Artifacts / Status / Review Details /Artifacts Removed and Rationale
No artifacts have been removed other than those defined in the [SDC DEVCS].
4.3.2 Business Modeling
Workflow
Inception artifacts will be updated to reflect the addition of IDOL scope.
Artifacts to Produce
As per the [SDC DEVCS], the following artifacts will be produced:
Table 4.3-3. Business Modeling Artifacts to Produce
Artifacts / Status / Review Details /Domain Model (Business Object Model) / Update / Formal-Internal
Business Use Case Model / Final / Formal-External
Artifacts Referenced from ECFS
None.
Artifacts Removed and Rationale
Refer to the ECFS DEVCS.
4.3.3 Requirements
Workflow
Inception artifacts will be updated to reflect the addition of IDOL scope. Requirements artifacts will be developed to specify the IDOL functionality.
Artifacts to Produce
As per the [SDC DEVCS], the following artifacts will be produced:
Table 4.3-4. Requirements Artifacts to Produce
Artifacts / Status / Review Details /Glossary / Update / None
Vision / Update / Formal – External
Requirements Database (EA)
• Requirements Attributes
• Stakeholder Requests
• Features / Update / None
Software Requirements Specification (detailed for specific use cases)
• Use-Case Model Survey
• Actor
• Use Case
• Use Case Package
• Diagrams (Use Case Model, Activity, Sequence, Collaboration)
• Detailed Use Cases
• Supplementary Specificiation / Update ECFS use cases
Initial IDOL use cases / Formal - External
Artifacts Referenced from ECFS
The following ECFS artifacts will remain unchanged .
Table 4.3-5. Requirements Artifacts Referenced from ECFS
Artifacts / Status / Review Details /Requirements Management Plan / See ECFS
Artifacts Removed and Rationale
No artifacts have been removed other than those defined in the [SDC DEVCS].
4.3.4 Analysis and Design
Workflow
There are no changes to the workflow as defined in the [SDC DEVCS].
Artifacts to Produce
As per the [SDC DEVCS], the following artifacts will be produced:
Table 4.3-6. Analysis & Design Artifacts to Produce
Artifacts / Status / Review Details /Deployment Model / Update / Peer
Software Architecture Document / Update / Peer
Artifacts Referenced from ECFS
None.
Artifacts Removed and Rationale
No artifacts have been removed other than those defined in the [SDC DEVCS].
4.3.5 Implementation
There are no implementation activities occurring during Inception.
4.3.6 Test
Test artifacts during this phase will be as defined for ECFS, as test artifacts for IDOL will be developed during the subsequent phase.
Workflow
During Inception, there will be no artifacts produced for the test discipline.
Artifacts Referenced from ECFS
The following ECFS artifacts will remain unchanged during Inception.
Table 4.3-7. Test Artifacts Referenced from ECFS
Artifacts / Status / Review Details /Test Guidelines / See ECFS
Test Automation Architecture / See ECFS
Artifacts Removed and Rationale
No artifacts have been removed other than those defined in the [SDC DEVCS].
4.3.7 Deployment
There are no deployment activities occurring in Inception.
4.3.8 Configuration and Change Management
Workflow
There are no changes to the workflow as defined in the [SDC DEVCS].
Artifacts to Produce
As per the [SDC DEVCS], the following artifacts will be produced:
Table 4.3-8. Configuration & Change Management Artifacts to Produce
Artifacts / Status / Review Details /Configuration Management Plan / Update / Peer
Change Request / New / Formal-External
Configuration Audit Findings / New / Peer
Project Repository / Update / Peer
Workspace / Update / Peer
Artifacts Referenced from ECFS
The following ECFS artifacts will remain unchanged during Inception.
Table 4.3-9. Configuration & Change Management Artifacts Referenced from ECFS
Artifacts / Status / Review Details /Artifacts Removed and Rationale
No artifacts have been removed other than those defined in the [SDC DEVCS].
4.3.7 Environment
Workflow
There are no changes to the workflow as defined in the [SDC DEVCS].
Artifacts to Produce
Table 4.3-10. Environment Artifacts to Produce
Artifacts / Status / Review Details /Development Case / Initial / Formal-Internal /
No additional Environment artifacts will be produced during this phase:
Artifacts Referenced from ECFS
The following ECFS artifacts will remain unchanged during Inception.
Table 4.3-11. Environment Artifacts Referenced from ECFS
Artifacts / Status / Review Details /Guidelines
• Design Guidelines
• Manual Styleguide
• Programming Guidelines
• Test Guidelines
• Tool Guidelines
• Use Case Modeling Guidelines
• User Experience Guidelines / See ECFS
Project-Specific Templates / See ECFS
Development Infrastructure / See ECFS
Development Organization Assessment / See ECFS
Tools / See ECFS
Artifacts Removed and Rationale
No artifacts have been removed other than those defined in the [SDC DEVCS].
1.4. Elaboration
This section defines the process that the Sierra System's IDOL Project Team will follow during Elaboration. The IDOL work that will occur during this phase will update existing artifacts produced during ECFS Elaboration, to reflect the added functionality of the IDOL system.
4.4.1 Project Management
Workflow
Inception artifacts will be updated to reflect the addition of scope.
Artifacts to Produce
As per the [SDC DEVCS], the following artifacts will be produced:
Table 4.4-1. Project Management Artifacts to Produce
Artifacts / Status / Review Details /Iteration Plan (Construction) / New / Formal-External
Iteration Assessment (Elaboration) / New / Peer-PRA
Software Development Plan / Update / Formal-External
Review Record / New. Many / None
Risk List (in Primavera) / Update / Peer - PRA
Issues List (in Primavera) / Update / Peer - PRA
Project Measurements (Primavera and Roundup) / Update / Peer – PRA
Status Assessment / New / Peer – PRA
Work Order (WBS in Primavera) / Update / None
Function Point Analysis (Estimated) / New / Formal-External
Artifacts Referenced from ECFS
None.
Artifacts Removed and Rationale
No artifacts have been removed other than those defined in the [SDC DEVCS].
4.4.2 Business Modeling
Workflow
Elaboration artifacts will be updated to reflect the addition of IDOL scope.
Artifacts to Produce
As per the [SDC DEVCS], the following artifacts will be produced:
Table 4.4-3. Business Modeling Artifacts to Produce
Artifacts / Status / Review Details /Domain Model (Business Object Model) / Update / Formal-Internal
Artifacts Referenced from ECFS
None.
Artifacts Removed and Rationale
No artifacts have been removed other than those defined in the [SDC DEVCS].
4.4.3 Requirements
Workflow
Elaboration artifacts will be updated to reflect the addition of IDOL scope. Requirements artifacts will be developed to specify the IDOL functionality.