detail training powerpoint slide deck
DESCRIPTION
TRANSCRIPT
Click to add textSUITE SEM Implementation
Detail Training
Workshop
State of Michigan • Department of Information Technology2
From Vision to Action
2
Today’s Topics SEM / SEM Express Overview
SEM Components SEM Stages (partitioning the project lifecycle) SEM Templates (documenting product requirements,
design, testing, and operational requirements) SEM Process Guides (processes for ensuring quality
and that approvals are obtained) SEM Touch Points (interfacing with other parties at the
appropriate times) Monitoring and Tracking Additional SEM Components
State of Michigan • Department of Information Technology3
From Vision to Action
3
What’s not covered in detail today
Why we are doing this – process training Training clients – each area has own plan Completing each template/form in detail How to “do” the steps e.g. how to “do” System
Design. SEM formalizes/documents current approaches.
Focus on best/MDIT practices will come later
State of Michigan • Department of Information Technology4
From Vision to Action
4
Where The SEM Fits In SUITE
SUITE will provide an integrated CMMI Level 3 compliant systems development framework that encompasses:
Project Management Systems Engineering (SEM) Process Management Support Processes
State of Michigan • Department of Information Technology5
From Vision to Action
5
Where Does SEM Fit In SUITE?
Systems Engineering
Project Management
Support Processes
Process Management
State of Michigan • Department of Information Technology6
From Vision to Action
6
SEM Overview
State of Michigan • Department of Information Technology7
From Vision to Action
7
Purpose of SEM
The Systems Engineering Methodology (SEM) provides guidance for information systems development related activities and software quality assurance practices.
The primary purpose of the SEM is to promote the development of reliable, cost-effective, computer-based solutions while making efficient use of resources.
State of Michigan • Department of Information Technology8
From Vision to Action
8
SEM ExpressSEM Express offers guidance for small and straight-
forward systems development projects. The intent of SEM Express is to provide an abbreviated methodology that ensures all necessary processes are performed and documented.
In general, the definition of “straight-forward” includes projects that: Continue to operate in the existing infrastructure environment and do
not involve procurement of additional infrastructure components; Utilize existing resources and do not procure services (except when
contractors are utilized as part of a multi-project initiative); Are developed for a single agency; Can be implemented without formal user training; Have little to no risk associated with them; and Have a low degree of exposure
State of Michigan • Department of Information Technology9
From Vision to Action
9
Touchpoints within SEMAgency Services
SEM
Processes & Templates
Project A
Project E
Project D
Project C
Project B
Project ..N
Infrastructure Services
Enterprise Security
Touch Points
Touch Points
Client Staff Requirmnts / Apprvls / Etc.
TimelyInteraction
TimelyInteraction
TimelyInteraction
Contracts & Procurement
Touch Points
TimelyInteraction
State of Michigan • Department of Information Technology10
From Vision to Action
10
Continual Improvement of SEM SEM Version 1.0 is the initial release of MDITs
Systems Engineering Methodology (formerly referred to as the Systems Development Life Cycle or SDLC).
It is expected that the SEM will improve and mature over the next several years, with much of that improvement expected in the next 6-12 months.
It is the responsibility of each of us to identify improvement opportunities to the methodology
State of Michigan • Department of Information Technology11
From Vision to Action
11
Who Can I Contact About SEM?
Michigan.gov/SUITE Your Manager/Project Manager Local IO Core team and SEM Champion(s) [email protected] – Routed to right responder SEM Change Form MDIT 0181
www.michigan.gov/suiteSUITE Team Room on TechTalk
(Projects –> MDIT –> SUITE)
State of Michigan • Department of Information Technology12
From Vision to Action
12
Stages of the SEM SEM Initiation and
Planning Requirements
Definition Functional Design Systems Design Construction Testing Implementation
SEM Express Initiation,
Requirements and Design
Construction and Testing
Implementation
State of Michigan • Department of Information Technology13
From Vision to Action
13
How SEM Documentation is Organized
State of Michigan • Department of Information Technology14
From Vision to Action
14
Consistent Sections For Each Stage
Description Inputs High Level Activities TouchPoints Outputs Review Process References Bibliography Stage Specific Processes
State of Michigan • Department of Information Technology15
From Vision to Action
15
Consistent Sections For Each Stage Description Inputs High Level Activities TouchPoints Outputs Review Process References Bibliography Stage Specific Processes
State of Michigan • Department of Information Technology16
From Vision to Action
16
Understanding SEM Templates
Templates - simple and flexible Designed for cutting, pasting and inserting Helpful instructions in “blue text” Easy to add rows/sections OK to mark some areas N/A Important Tip – Don’t Delete the MDIT “clippy” - includes helpful tools
State of Michigan • Department of Information Technology17
From Vision to Action
17
Consistent Sections For Each Stage
Description Inputs High Level Activities TouchPoints Outputs Review Process References Bibliography Stage Specific Processes
State of Michigan • Department of Information Technology18
From Vision to Action
18
New Concepts Touchpoints
Security Procurement Infrastructure Services
Enterprise Architecture, Solutions Engineering & Telecom
Business Continuity Planning
Process Guides Structured Walkthrough Stage Exit
State of Michigan • Department of Information Technology19
From Vision to Action
19
Features of the Overview Chart
Simplest way to understand SEM One-Stop Shopping Detail and Big Picture Views on One Page Hot Links to stages, templates and process guides
Highlight stages Show “consistent sections” within each stage “Outputs” include revised as well as final documents
Templates (blank and sample) Process Guides
Structured Walk Though Stage Exits (Deliverables)
Available at www.michigan.gov/suite --> SEM
State of Michigan • Department of Information Technology20
From Vision to Action
20
SEM and SEM Express
State of Michigan • Department of Information Technology21
From Vision to Action
21
State of Michigan • Department of Information Technology22
From Vision to Action
22
State of Michigan • Department of Information Technology23
From Vision to Action
23
Initiation and Planning StageDescription:
First lifecycle stage Project Management Methodology (PMM) and SEM are
tightly integrated. Most outputs are PMM documents - Participation of the
business client is critical ! Business Case Project Charter Project Plan Quality Management Plan.
Two SEM documents are started Software Configuration Management Plan Maintenance Plan
State of Michigan • Department of Information Technology24
From Vision to Action
24
Stages of the SEM SEM Initiation and
Planning Requirements
Definition Functional Design Systems Design Construction Testing Implementation
SEM Express Initiation,
Requirements and Design
Construction and Testing
Implementation
State of Michigan • Department of Information Technology25
From Vision to Action
25
Initiation and Planning StageInputs:
Requirements identified in project related materials, (e.g., a business case)
Related project initiation materials
State of Michigan • Department of Information Technology26
From Vision to Action
26
Initiation and Planning StageHigh Level Activities:
3.1 Develop Software Configuration Management Plan
3.2 Develop Maintenance Plan
State of Michigan • Department of Information Technology27
From Vision to Action
27
Initiation and Planning StageTouchpoints:
Contracts and Procurement Assignment of a Contract Liaison if procuring goods or services Completion on DIT-0153 Bid Information Sheet if procuring goods or
services Enterprise Architecture (EA)
Review relevant EA materials (e.g., roadmaps, solution patterns) Develop EA Solution Assessment for each alternative (refer to Appendix
C for assistance in developing the EA Solution Assessment. Security
Notify your Security Liaison of project initiation Review MDIT and Agency Security Policies Initiate Security Plan, including Data Classification and System Criticality
sections Other
Initiate Business Continuity Planning process (DMB has a website for this purpose.)
State of Michigan • Department of Information Technology28
From Vision to Action
28
Initiation and Planning StageOutputs:
SEM Templates: Software Configuration Management Plan (initial) Maintenance Plan (initial)
PMM Templates: Business Case Concept Document (i.e., Feasibility Study) Project Charter Project Plan (includes Quality Management Plan)
Other Outputs: Security Plan (initial) Enterprise Architecture (EA) Solution Assessment for each
potential solution option (initial) Business Continuity Plan (initial)
State of Michigan • Department of Information Technology29
From Vision to Action
29
Requirements Definition StageDescription:
Develop mutual understanding between business owner/users and project team about the requirements for the project.
Analyze business needs and translate into formal requirements.
Approved Requirements Specification = initial baseline for product design
Approved Requirements Specification = reference for determining whether the completed product performs as the system owner requested and expected.
All system requirements, (e.g., software, hardware, performance, functional, infrastructure, etc.) should be included.
Plan testing activities to validate product performance.
State of Michigan • Department of Information Technology30
From Vision to Action
30
Requirements Definition StageInputs:
SEM Templates: Software Configuration Management Plan Maintenance Plan
PMM Templates: Business Case Concept Document (i.e., Feasibility Study) Project Charter (Statement of business objectives) Project Plan (includes Quality Management Plan)
Other Inputs: Security Plan Enterprise Architecture (EA) Solution Assessment for each
potential solution option
State of Michigan • Department of Information Technology31
From Vision to Action
31
Requirements Definition StageHigh Level Activities:
4.1 Requirements Management 4.2 Select Requirements Analysis Technique 4.3 Define System Requirements 4.4 Compile/Document System Requirements 4.5 Develop System Test Requirements 4.6 Develop Acceptance Test Requirements 4.7 Establish Functional Baseline
State of Michigan • Department of Information Technology32
From Vision to Action
32
Requirements Definition StageTouchpoints:
Contracts and Procurement Completion of DIT-0015a, if procuring commodities (e.g., servers, software) Completion of DIT-0015b (including Statement of Work and Requirements
Traceability Matrix), if procuring services (e.g., project management, application developers)
Utilize the services of the assigned Contract Liaison, if procuring services Enterprise Architecture (EA)
Use relevant EA materials (e.g., roadmaps, solution patterns) while developing Technical Requirements
Revise/complete EA Solution Assessment for each alternative Refer to the EA TechTalk portal site
Infrastructure Services When EA Solution is complete and approved, prepare Infrastructure Services
Request (ISR), and begin Hosting Solution document Security
Review MDIT and Agency security policies Review State and Federal laws and regulations Begin Infrastructure/Network and Data Flow Diagram
State of Michigan • Department of Information Technology33
From Vision to Action
33
Requirements Definition StageOutputs:
SEM Templates: Requirements Specification (initial) Requirements Management Checklist Requirements Traceability Matrix (initial) Maintenance Plan (revised) Software Configuration Management Plan (revised)
PMM Templates: Project Plan (revised)
Other Outputs: Security Plan (revised) Application Hosting document (initial) Business Continuity Plan (revised) EA Solution Assessment (final) Infrastructure Services Request (final)
State of Michigan • Department of Information Technology34
From Vision to Action
34
Functional Design StageDescription:
Maps the "what to do" of the Requirements Specification into the "how to do it" of the design specifications.
Define product structure from a functional viewpoint. Describe logical system flow, data organization, system
inputs and outputs, processing rules, and operational characteristics of the product from the user's point of view.
Define and document product functions to obtain system owner and users understanding and approval.
Define and document product functions to the level of detail necessary to build the system design.
.
State of Michigan • Department of Information Technology35
From Vision to Action
35
Functional Design StageInputs:
SEM Templates: Maintenance Plan Requirements Specification Requirements Traceability Matrix Software Configuration Management Plan
PMM Templates: Project Plan Quality Management Plan
Other Inputs: Security Plan Business Continuity Plan MDIT Hosting Solution Document
State of Michigan • Department of Information Technology36
From Vision to Action
36
Functional Design StageHigh Level Activities:
5.1 Determine System Structure 5.2 Design Content of System Inputs and Outputs 5.3 Design User Interface 5.4 Design System Interfaces 5.5 Design System Security Controls 5.6 Build Logical Model 5.7 Build Data Model 5.8 Develop Functional Design 5.9 Select System Architecture
State of Michigan • Department of Information Technology37
From Vision to Action
37
Functional Design StageTouchpoints:
Contracts and Procurement Contract liaison involvement in the process, if contract
issues arise Infrastructure Services
Review and complete Hosting Solution document Security
Review MDIT and Agency security policies Review State and Federal laws and regulations Review existing or propose new security controls Conduct preliminary risk analysis Revise Infrastructure/Network and Data Flow Diagram
State of Michigan • Department of Information Technology38
From Vision to Action
38
Functional Design StageOutputs:
SEM Templates: Functional Design Document (final) Maintenance Plan (revised) Requirements Specification (final) Requirements Traceability Matrix (revised) Software Configuration Management Plan (revised)
PMM Templates: Project Plan (revised)
Other Outputs: Security Plan (revised) Business Continuity Plan (revised) Data Dictionary (final) MDIT Hosting Solution Document (final)
State of Michigan • Department of Information Technology39
From Vision to Action
39
System Design StageDescription:
Translate the user-oriented Functional Design into a set of technical, computer-oriented system design specifications.
Design the data structure and processes to the level of detail necessary to plan and execute the Construction and Implementation Stages.
Produce general module specifications that define what each module is to do, but not how the module is to be coded.
Provide a blueprint for the coding of individual modules and programs.
State of Michigan • Department of Information Technology40
From Vision to Action
40
System Design StageInputs:
SEM Templates: Functional Design document Maintenance Plan Requirements Specification Requirements Traceability Matrix Software Configuration Management Plan
PMM Templates: Project Plan Quality Management Plan
Other Inputs: Security Plan Data Dictionary
State of Michigan • Department of Information Technology41
From Vision to Action
41
System Design StageHigh Level Activities:
6.1 Design Specifications for Modules 6.2Design Physical Model and Database
Structure 6.3 Develop Integration Test Considerations 6.4 Develop System Test Considerations 6.5 Develop Conversion Plan 6.6 Develop System Design 6.7 Develop Program Specifications
State of Michigan • Department of Information Technology42
From Vision to Action
42
System Design StageTouchpoints:
Contracts and Procurement Contract Liaison involvement if contract issues arise
Enterprise Architecture (EA) Request exceptions as required Complete EA Solution Assessment for the chosen solution and submit to
EA for review/approval Infrastructure Services
Technical and Data Center Services Solutions Engineer involvement in completion of Hosting Solution document
Infrastructure Specialist involvement in establishing the construction environment
Security Review MDIT and Agency Security Policies Review State and Federal Laws and Regulations Revise Network Diagram and Data Flow Diagrams Review Final Risk Analysis with OES recommended security controls
State of Michigan • Department of Information Technology43
From Vision to Action
43
System Design StageOutputs:
SEM Templates: Conversion Plan (initial) Maintenance Plan (revised) Requirements Traceability Matrix (revised) Software Configuration Management Plan (final) Software Testing Checklist (final) System Design Checklist (final) System Design Document (final) Test Plan (initial) Test Reports (initial)
Other Templates: Project Plan (revised) Security Plan (revised)
State of Michigan • Department of Information Technology44
From Vision to Action
44
Construction StageDescription:
Translate System Design into a language the computer can understand and execute.
Construction involves coding, validation and unit testing by a developer.
Install hardware or software procured to support the construction effort.
Develop plans for installation of the operating environment hardware and software.
Design a training program and create a Training Plan. Produce operating documentation for installing,
operating, and supporting the product through its lifecycle.
State of Michigan • Department of Information Technology45
From Vision to Action
45
Stages of the SEM SEM Initiation and
Planning Requirements
Definition Functional Design Systems Design Construction Testing Implementation
SEM Express Initiation,
Requirements and Design
Construction and Testing
Implementation
State of Michigan • Department of Information Technology46
From Vision to Action
46
Construction StageInputs:
SEM Templates: Conversion Plan Functional Design Document Maintenance Plan Requirements Specification Requirements Traceability Matrix System Design Document Test Plan Test Reports
PMM Templates: Project Plan Quality Management Plan
Other Inputs: Security Plan Data Dictionary
State of Michigan • Department of Information Technology47
From Vision to Action
47
Construction StageHigh Level Activities:
7.1 Establish Development Environment 7.2 Develop Programs 7.3 Conduct Unit Testing 7.4 Establish Development Baselines 7.5 Plan Transition to Operational Status 7.6 Generate Operating Documentation 7.7 Develop Training Plan 7.8 Develop Installation Plan
State of Michigan • Department of Information Technology48
From Vision to Action
48
Construction StageTouchpoints:
Contracts and Procurement Contract Liaison involvement if contract issues arise
Infrastructure Services Infrastructure Specialist involvement in establishing
hosting environments
Security Finalize Network and Data Flow diagrams
State of Michigan • Department of Information Technology49
From Vision to Action
49
Construction Stage Outputs: SEM Templates:
Conversion Plan (revised) Installation Plan (initial) Maintenance Plan (revised) Requirements Traceability
Matrix (revised) Test Plan (final) Test Reports (revised) Training Checklist (final) Training Plan (initial) Transition Plan (initial)
PMM Templates: Project Plan (revised)
Other Outputs: Security Plan (revised) Development baselines Operating Documentation
Users Manual Developer's Reference Manual
Project Test File System units and modules
State of Michigan • Department of Information Technology50
From Vision to Action
50
Testing StageDescription:
Testing activities focus on interfaces between and among components of the product, such as functional correctness, system stability, overall system operability, system security, privacy and sensitive information control, and system performance requirements.
Integrate components and conduct Integration Testing to determine whether the product meets predetermined functionality, performance, quality, interface, and security requirements.
Once the product is fully integrated, conduct System Testing to validate that the product will operate in its intended environment, satisfies all user requirements, and is supported with complete and accurate operating documentation.
After successful System Testing, conduct User Acceptance Testing (UAT) to identify any final product adjustments before implementation.
State of Michigan • Department of Information Technology51
From Vision to Action
51
Testing Stage Inputs: SEM Templates:
Conversion Plan Installation Plan Maintenance Plan Requirements Specification Requirements Traceability
Matrix Test Plan Integration testing (component
to component) Performance testing (load,
stress, etc.) System testing (end to end) User acceptance testing (UAT)
Test Reports Integration test reports Performance test report System test reports User Acceptance test reports
Transition Plan Training Plan
PMM Templates: Project Plan Quality Management Plan
Other Inputs: Security Plan Development Baselines Operating Documentation
Users Manual Developer's Reference Manual
Project Test File Software Modules
State of Michigan • Department of Information Technology52
From Vision to Action
52
Testing StageHigh Level Activities:
8.1 Conduct Integration Testing 8.2 Conduct System Testing 8.3 Conduct User Acceptance Testing
State of Michigan • Department of Information Technology53
From Vision to Action
53
Testing StageTouchpoints:
Contracts and Procurement Contract Liaison involvement if contract issues arise
Infrastructure Services Infrastructure Specialist involvement as documented
in the Infrastructure Services Request (ISR)
Security Include application testing for security controls
State of Michigan • Department of Information Technology54
From Vision to Action
54
Testing StageOutputs:
SEM Templates: Error Reporting and Tracking
Checklist (final) Integration and System Testing
Checklist (final) Pre-acceptance Checklist (final) Testing Package Checklist (final) User Acceptance Checklist (final)
Conversion Plan (revised, if needed)
Installation Plan (final) Maintenance Plan (revised) Requirements Traceability Matrix
(final) Test Reports (final)
Integration test reports Performance test report System test reports User Acceptance test reports
Training Plan (final) Transition Plan (revised)
PMM Templates: Project Plan (revised)
Other Outputs: Security Plan (revised) Operating Documents (final)
Users Manual Developer's Reference Manual
State of Michigan • Department of Information Technology55
From Vision to Action
55
Implementation StageDescription:
Implementation of the product is initiated after all application testing has been successfully completed.
This stage involves the activities required to install the software, databases, or data that comprise the product onto the hardware platform at the site(s) of operation.
User training may be required to complete the implementation process. A description of the training necessary for developers, testers, users, and operations staff is provided in the Training Plan.
State of Michigan • Department of Information Technology56
From Vision to Action
56
Stages of the SEM SEM Initiation and
Planning Requirements
Definition Functional Design Systems Design Construction Testing Implementation
SEM Express Initiation,
Requirements and Design
Construction and Testing
Implementation
State of Michigan • Department of Information Technology57
From Vision to Action
57
Implementation StageInputs:
SEM Templates: Conversion Plan Installation Plan Maintenance Plan Training Plan Transition Plan
PMM Templates: Project Plan Quality Management Plan
Other Inputs: Security Plan Operating Documents
Users Manual Developer's Reference Manual
State of Michigan • Department of Information Technology58
From Vision to Action
58
Implementation StageHigh Level Activities:
9.1 Perform Installation Activities 9.2 Conduct Installation Tests 9.3 Transition to Operational Status
State of Michigan • Department of Information Technology59
From Vision to Action
59
Implementation StageTouchpoints:
Contracts and Procurement Contract Liaison involvement to close out all open
contracts and/or purchase orders related to this systems development effort
Security Work with the MDIT Security Liaison to finalize and
get final signoff of the Security Plan (DIT-0170)
Other Finalize the Business Continuity Planning process.
State of Michigan • Department of Information Technology60
From Vision to Action
60
Implementation StageOutputs:
SEM Templates: Conversion Plan (final) Maintenance Plan (final) Transition Plan (final)
PMM Templates: Project Plan (final) Post Implementation Evaluation Report (PIER) (final)
Other Outputs: Security Plan (final) Converted data or system files Installation Test materials Operating documents Operational software product
State of Michigan • Department of Information Technology61
From Vision to Action
61
State of Michigan • Department of Information Technology62
From Vision to Action
62
SEM TailoringThe intent of SEM tailoring guidelines, found in SEM
Chapter 2, is to provide flexibility in utilizing SEM components in the systems development process. The focus here is to ensure that adequate processes are used for each of the various types of systems engineering initiatives – “using the right tool for the job.”
State of Michigan • Department of Information Technology63
From Vision to Action
63
Template Exercise/Break Review the blank and completed template for
“Requirements” In small groups
Discuss how the form should be completed Captain” (person w/lightest shirt) to report out on
How it felt using the new process How is it the same/different What do they need to make it a success Difference between Clients role and MDIT role
Complete assignment and take break w/in 25 min
State of Michigan • Department of Information Technology64
From Vision to Action
64
Process Guides
State of Michigan • Department of Information Technology65
From Vision to Action
65
Why are we doing this? Consistent, standard, repeatable processes Collection of best practices Identify defects before they get to production Decrease cost Increase productivity and quality Improve Communication Improve on-time and on-budget delivery our
clients Avoid late engagement from stakeholders
State of Michigan • Department of Information Technology66
From Vision to Action
66
SEM Processes (linked)
Structured Walkthrough Process Guide A guide to assist the project team with a formal process on how to ensure a deliverable is complete and of acceptable quality. A Structured Walkthrough is required for every major project deliverable.
Stage Exit Process Guide A guide to assist the project team on how to transition from one SEM stage to the next. Required before moving to the next stage (e.g., Requirements Definition to Functional Design).
State of Michigan • Department of Information Technology67
From Vision to Action
67
Structured Walkthrough Process Guide
State of Michigan • Department of Information Technology68
From Vision to Action
68
Structured Walkthrough Process Guide
A structured walkthrough is an organized procedure for a group of peers to review and discuss the technical aspects of software development work products.
“The number of errors in production systems decreases by as much as 90% in organizations that use walkthroughs diligently.”
State of Michigan • Department of Information Technology69
From Vision to Action
69
Structured Walkthrough Process Guide
The major objectives Find errors & omissions as early as possible Improve the quality of the product
Structured Walkthrough Meeting Record Structured Walkthrough Management Summary
Report.
State of Michigan • Department of Information Technology70
From Vision to Action
70
Structured Walkthrough RolesDetailed /Definitions in Notes
Author Presenter Moderator Reviewers Scribe
State of Michigan • Department of Information Technology71
From Vision to Action
71
When is a Structured Walkthrough (SWT) Required?
On all major stage exit deliverables (see SWT Process Guide page 18+)
Initiation and Planning Stage: Project Plan Security Plan Software Configuration Management Plan Maintenance Plan, if needed
Requirements Definition Stage: Requirements Specification Document Requirements Traceability Matrix Security Plan
Etc…
State of Michigan • Department of Information Technology72
From Vision to Action
72
Stage Exit Process Guide
State of Michigan • Department of Information Technology73
From Vision to Action
73
Stage Exit Documentation
State of Michigan • Department of Information Technology74
From Vision to Action
74
Stage Exit Process Guide Assists the project team with the Exit Approval
Process. Assists the project team in securing the approval by
designated individuals to continue with the project and move forward into the next stage of development.
The Exit Approval indicates that all documents related to that stage have been approved and that there are no outstanding issues.
Stage Exit Position Response Form
State of Michigan • Department of Information Technology75
From Vision to Action
75
Stage Exit Participants
Systems Engineering Team System Owner/Sponsor's) Client point of contact (POC) Software Quality Assurance (SQA) Enterprise Architecture (EA) Office of Enterprise Security (OES) Infrastructure Services (IS) Others, as appropriate
State of Michigan • Department of Information Technology76
From Vision to Action
76
What Do I Need to Actually Do
Follow the overview documents Complete the Templates for the Stage Complete the Structured Walkthrough Obtain “Sign-Offs” on all templates Complete the Stage Exit when all areas sign off Use SEM Process for Continuous Improvement
State of Michigan • Department of Information Technology77
From Vision to Action
77
Monitoring and Tracking
Bi-weekly reporting on SEM implementation Validation that Stage Exit documents are
complete Validation that Stage Exit documents conform
to the Software Configuration Management Plan
SUITE Core Team reviews reports and feedback on SEM usage
State of Michigan • Department of Information Technology78
From Vision to Action
78
Additional SEM Components
State of Michigan • Department of Information Technology79
From Vision to Action
79
SEM Systems Maintenance Guidebook
Offers guidance on system maintenance, including a section on Release Management
Refers the user back to existing SEM / SEM Express documents (templates) for the purposes of updating the documents (such as the Requirements Specification document)
State of Michigan • Department of Information Technology80
From Vision to Action
80
Additional SEM Workshops
Software Configuration Management Requirements Gathering Estimating Structured Walkthrough & Stage Exit
Processes Security Plan
State of Michigan • Department of Information Technology81
From Vision to Action
81
Thoughts? - Questions?During Implementation
Michigan.gov/SUITE Your Manager/Project Manager Local IO Core team and SEM Champion(s) [email protected] – Routed to right responder
Software Engineering Process Group) SEM Change Form MDIT 0181
www.michigan.gov/suiteSUITE Team Room on TechTalk
(Projects –> MDIT –> SUITE)
State of Michigan • Department of Information Technology82
From Vision to Action
82
State of Michigan • Department of Information Technology83
From Vision to Action
83
Handouts
SEM Trifold Slides as handouts – Print 4 or 6 per page
double sided / stapled Template and Sample for Requirements SEM Template JobAid SEM Express (19 pages – includes SEM
Express Overview Diagram)