System Engineering Management Plan

Jon Harrah
May 12, 2014
CTU
CS672 Systems Engineering Methods
Professor N. Abbas
Phase 5

Document History Distribution

Revision History
Re
visi
on
#
1.
0
1.
1

Revisio
n Date

Description of Change

Author

04/20
/14
04/29
/14

Initial Document

J. Harrah

1.
2
1.
3

05/04
/14
05/11
/14

Addition of
Configuration
Management
o Requirement
Engineering
o Functional Analysis
Specialty Engineering
o

Executive Summary

J. Harrah

J. Harrah
J. Harrah

Distribution
Recipient Name

Recipient Organization

Distribution Method

Plan Approvers
Identify the plan approvers. List the name, signature and date the plan was approved.

Approver Name Approver Signature Approval Date Approval Group Represented

Executive Summary

This document is to present an outline of system engineering management plan that will
guide stakeholder, in-house employees and contractors of their duties that will occur as the
project unfolds. This plan is a complex plan that is need for 1st Source Solution to provide
services and solution to local governments. The SEMP take the requirements presented by
stakeholders and transform them into the system and application that is needed to accomplish the
goals.
The upgrade of legacy hardware systems to new modern technology that will provide
customer services to both the clients and employees in the development of the application, setup
and deployment. This new hardware upgrade will provide power, speed and advantages over
competitors. By providing proven success, stability and ongoing enhancements it will show to
the clients. The continuous investing to improve the application to manage solution is in
responce to listing and responding to our customers with new functions.
The software solutions presented in this plan incorporates the demands and request that
are needed to assure that the clients are protected and are provide reliable system services. The
new web servers and redundancy backup allows for the client to be reassured of such service by
using 1st Source Solution for their local government document management system.

The goal of this plan is to establish guidelines, methods and best practices to manage and
effectively execute the system engineering management plan.

Table of Contents
Document History Distribution...........................................................................................2
Revision History..........................................................................................................2
Distribution..................................................................................................................2
Plan Approvers.............................................................................................................2
Executive Summary.............................................................................................................3
Introduction..........................................................................................................................7
Purpose................................................................................................................................7
Document Overview........................................................................................................7
System Overview.............................................................................................................7
Project Schedule..............................................................................................................8
System Engineering Processes............................................................................................9
Project Organization........................................................................................................9
Roles & Responsibilities................................................................................................10
Project Roles Table....................................................................................................10
Environments.................................................................................................................12
Decision-Making Process..............................................................................................13
Objective........................................................................................................................14
Alternatives....................................................................................................................14
Alternative Table........................................................................................................14

Making Choice...............................................................................................................15
System Engineering Model................................................................................................16
System Engineering Processes......................................................................................17
Configuration Management...........................................................................................17
Requirements Engineering.........................................................................................17
Functional Analysis...................................................................................................18
Design Processes...........................................................................................................18
Development Processes.................................................................................................18
Verification....................................................................................................................19
Validation...................................................................................................................19
Specialty Engineering........................................................................................................19
System Deployment...........................................................................................................20
Site preparation..............................................................................................................20
System installation.........................................................................................................20
System checkout............................................................................................................21
User training..................................................................................................................21
Product Support.................................................................................................................22
Maintenance...................................................................................................................22
Logistics support............................................................................................................22
Disposal.............................................................................................................................22

References..................................................................................................................24

Introduction
1st Source Solution is acquiring the need for a new computer system to update the legacy
outdated system that has been running for the past eighteen years. The required update is to
allow for 1st Source Solution to compete with the growing trends and markets for government
document systems. The system engineering management plan will need to accomplish the
business model and aspects for the company to accomplish the logistics and methods required to
provide clients with secure web applications, remote diagnostics, emails and file management
system.

Purpose
System Engineer Management Plan shall describe the contractors efforts for planning
and controlling a fully integrated effort in engineering of system. The SEMP is to be used to
evaluate the engineering efforts as a monitoring process in the system to provide detail to project
managers, engineers, software developers and stakeholders of the progression of the system.

Document Overview
The SEMP will be a map for the system information that is of high level overview that
will provide document history, table of contents, an introduction, schedule, system overview,
decision process, models to be used, functionality, design process, development process,
implementation, build management, product support and disposal.

System Overview

The SEMP will require the engineers to move information and data from legacy systems
to hybrid systems. This is to have systems interact with sub-systems to provide efficiency to the
clients they serve. The architecture of the system is to move from old AS/400 IBM database
servers to new Microsoft MSSQL database system. The web introduction is to provide new
servers to handle the web interface for client portals and web applications. The clients are
moving away from in-house IT departments and outsourcing to subscription as service base, this
provides less overhead for IT personal. This shift in is coming into concepts with governments
having to cut budgets and support. The SAS is allowing for 1st Source to pick up new clients
with this evolution the need for new hardware, software and support personal is needed to be
added and updated.
This system is required to provide redundancy and precision execution to multiple
backup locations across the U.S. The redundancy need to provide daily backup of client data and
provide web servers that run in tandem incase one goes down the other are not affected.

Project Schedule
The SEMP schedule will be a series of milestones that are too provided in such as to
starting and completing dates of each of the requirements; with the understanding that the detail
of each area will provide explicit dates of completions. The implementation of this plan is to
cover the longevity of the project. Time required to complete this plan is twenty-four months
and this is broken down into the following:
1. System Engineering Process
4 months
2. Specialty Engineering
6 months
3. System Deployment
7 months
4. Product Support
4 months
5. Disposal
3 months
Each of the five areas will be detailed out by the project manager to schedule the appropriate
vendors and suppliers to accomplish the plan.

System Engineering Processes

Project Organization
The project is based around building a team of experts that have knowledge and
experience in designing and developing systems and software, since this will have both
involvements the team concept will require a vast amount of personal to meet the requirements
that are presented. The SMEP will be providing a table with a high level overview of what is
required from the different aspects in the project. This plan will gather sub-contractors, vendors
and house staff to accomplish it. The understanding of geo-location of the different parties
involved will require communication amounts each to prevent a laps in direction.
The responsible parties from each unit will require meeting on a regular base via web
meeting for out of town personal and interring office meeting for local participants. The SE will
be required to communicate with the PM and the stakeholders with the status of the
development. There will be technical requirements to handle the management of the project that
will provide outlines, boundaries and interfaces and responsibilities to provide the best results in
the plan.
The system engineer and the project manager has two totally different roles there are
some items within the plan that will overlap it will be the SE to be to facilitator to the PM of the
overall aspects of the plan. The SE will oversee the entire development of the project and plan
and within the plan there will be multiple project managers that are specific departments or
phases facilitators. This is where the PM will have hands on the specific area of the plan; there

will be project managers that will handle the development of the hardware upgrades, software
development and the security.

Roles & Responsibilities

The function of matrix will be based on the depicted project responsibility and it shows
the responsibility of the department that will accomplish the description of tasks. The teams will
report to their prospective PM that will report the SE. The SE will report to the Stakeholders.
Project Roles Table
Project Role
Sponsor

Description

CIO
COO
Computing Services Executive

Software & Systems

Integration Director

Operations Director

Operations Manager

Telecommunications Services

Executive

Network Monitoring Manager

Network Design & Support

Firewalls

Sustain executive and organizational

commitment and support for the project.
Communicate business direction
changes to senior management.
Executive officer for ITS.
Executive officer for ITS hosting.
Sustain executive and organizational
commitment and support for the
application rollout for hardware and OS
components
Communicate business direction
changes to ITS senior management for
hardware and OS components
Responsible for delivering infrastructure
needed to support environments hosted
at ITS.
Provide daily operational support for the
environments at ITS.
Responsible for supporting data center
environmental needs for applications
hosted at ITS.
Provide daily operational support for the
environments at ITS.
Provide daily platform monitoring and
management of HW & OS.
Responsible for coordinating with the
project team to provide power and space
for hardware needed.
Oversees ITS Telecommunications and
Networking.
Oversees Network Monitoring Team.
Company IP Network
IP Data Services
Security Services
Network Management
Design network infrastructure
Support network infrastructure
Configure firewall to meet application
needs and follow security protocols

ITS Resource

Other Agency Resource

Dependencies

X
X
X

Project Role
Project Manager

Description

PMO Office

Technical Project Integrator

Service Coordinator Manager

CS Project Coordinator

Customer Service

Representatives
IT Database Manager

Database

UNIX
INTEL

Hold initial meeting to explain concept,

approach, roles, and timeline
Maintain open communication with all
groups.
Utilize standard and procedures.
Coordinate activities among multiple
parties.
Publish documents to respective parties.
Overall project status reporting.
Assist with project planning.
Assist with project schedule planning.
Assist with project communication.
Assist with project risk assessment and
risk mitigation planning.
Assist with post project reviews.
Provide leadership on the technical
components of the project.
Ensure communication and collaboration
among the technical teams working on
implementation and ongoing support.
This will include managing cooperative
relationships with the project team
members and vendors.
Enable ITS to establish a hosting
environment that is architected,
deployed, and maintained in a manner
that meets or exceeds SLAs to be
established between parties.
Responsible for providing service
coordination for the Computer Services
division.
Support PM & Technical Integrator on all
project activities for the Computing
Services group at ITS.
Follow identified processes to serve
customers.
Responsible for managing database
services for databases located at ITS.
Manage Database Resource.
Monitor system traffic.
Trouble shoot any DB issues.
Manage UNIX environment.
Trouble shoot any UNIX issues.
Manage INTEL environment.
Trouble shoot any UNIX issues.

IT Storage Management

Manager
Storage Design

Responsible for managing storage

management team.

Architect & design storage plan.

Storage Operations

Manage SAN environment.

IT Systems Planning and

Design Manager
Server Performance &

Responsible for managing systems

planning and design team.

Server & CPU monitoring.

Capacity
Backup Design

Define backup strategy/ methodology.

Backup Operations

Administer and monitor backup process.

Disaster Recovery

Define Disaster recovery strategy /

methodology.

ITS Resource

Other Agency Resource

Dependencies

X
X
X
X
X
X
X

X
X

X
X
X
X

Project Role

Description

Procurement

Administer and monitor DR process.

Hardware / Software purchases.

Platform Security /

Vulnerability Scans
Platform Services

Scan OS to identify any security

vulnerability issues and create baseline
metrics.
MAPS (Managed Application Platform
Services) - load and manage the OS and
most of the services it provides.
Manage and monitor the hardware
deployed by NOS (Solaris/Unix,
Windows, Netware/Linux, etc).
Name the servers and prepare the
Server Farm Request forms that TS
requires for IP address assignment and
firewall rule generation.
Responsible for power and AC.

Facilities

ITS Resource

Other Agency Resource

Dependencies

X
X

Environments
The development of the environment will require different tools to be used to provide
adequate design, coding, documentation, and communication to be presented throughout this
plan. The development of the software will use IDE such as Komoto IDE with Git Hub
repository for version control. The designing of the interface will be presented to stakeholder in
storyboard from Photoshop for a quick and visual understanding of the functions of each
interaction part of the software. The hardware development will use flow charts to provide a
map of the architecture and give suggestions of model numbers. The communication and
documentation will be done using Google Docs, Google Scheduler and Google Drive for
collaboration. The Get Hub repository can be set up to accept the Google Drive files
automatically. In using Google Docs, there will be documents for communication plan
templates, meeting minutes templates; issues log template, weekly project status report template
and sign in sheet templates for Get Hub. The handoff of each phase of the work throughout this
plan will be followed with a written document that encompasses the work and the versions of
changes to the SE for sign off from the stakeholders.

Decision-Making Process
The stakeholder request that there be an update to hardware and software to provide users
with the capabilities to preforming efficiently in their jobs to process permits, business licenses
and process utility billing. The problem is the legacy system is over twenty years old. The
current system runs on AS/400 DB2 database and it does not provide access to internet for users.
The servers are running Windows Server 2003 and the client interface is green screens that have
been adapted to Windows XP environment.
This plan has be triggered by users complaining about not getting the required
information on a specific customer, and the constituents requiring internet access due to other
area municipalities having technology to do so. The problem has arrived due to lack of IT
inference on keeping technology up to date as well as yearly budget cuts due to poor economy.

Objective
The concern with this project has many facets but they will provide an understanding of
concerns, decisions and solutions in the following table.
Cost

Reluctant to update produce a

legacy system that is going to
cost more the longer it is put

Time Frame

off.
The amount of time to have

Security of Data on web

the project up and running.

Concerns with data being

Training

secure on the web

Concerns with training all
users and the resentment of

Hardware interface

change to something new.

What if the hardware does not
communicate with older

Reliability

hardware on the system?

How reliable will the system
be over the internet and offsite storage in the event of
natural disaster?

Alternatives
The alternatives to the objectives are to provide the stakeholders with a selection to
achieve the directives from the request and requirements that are present. The primary concerns
is the cost of the project and this being the case of neglect for so long it will be inevitable that it
is to perceive. The cost of such project is going to continue to grow the longer the client puts off
the upgrade, but within the plan there is an alternative to the development of the software that is
need for the end user. This can be accomplished in several manors being as follows:

Alternative Table
Objective
Cost

Specifics
Reluctant to update produce a

Alternatives
1. Develop a hybrid system

legacy system that is going to

were an off the shelf is

cost more the longer it is put

changed to fit the needs of

off.

the requirements.
2. Use an off the shelf product
from a vendor that is

limited on customizing to
fit the needs but may
Time Frame

The amount of time to have

accomplish the directives.

1. The design and addition of

the project up and running.

hardware will require be

designing, implementing
and testing.
2. Upgrade existing servers
with new operating
systems to handle the new
database and web service.
3. Add virtual servers to save
time and cost, by moving
minimal uses systems to

Security of Data on web

Concerns with data being

secure on the web

combined virtual servers.

1. Contract with 3rd- party to
host backups.
2. Use products such as
Google Drive for Business
to automatic backup files

Training

Concerns with training all

of the server.
1. Provide webinar training
2. Host training videos that

users and the resentment of

employees can view as
change to something new.
needed.
3. Have training forums for
employees to discuss

issues.
4. Provide train the trainers
program to provide
Hardware interface

What if the hardware does not

individual help.
1. Upgrade the existing

communicate with older

hardware with the same

hardware on the system?

vendor for compatibility.

2. Look at Intelligent Platform
Management interface (IPMI)

Making Choice
The decision of this plan will be a collective effort based on the expertise of those that are
involved in the project, the advice form the expertise will be taken under advisement by the
stakeholders. The communication among the SE and PMs is to provide an effective decision that
provides the project with the right choice to solve the problem.

System Engineering Model

The iterative development is the method that will be used in the development process of
this project. The iterative development divides the project into smaller projects which allows for
quicker results and builds upon the prior directive that are completed. The developers will be
provided with feedback quicker as the small objectives are qualified, the valuable feedback from
the users is essential. The iterative is a mini-waterfall that returns feedback on the phase at hand
and it provides information for the next phase. The iterative method will produce a product that
can go into product that can become into production upon approval of the phase and be
incremental releases.

The decision of using iterative is the ability to analysis requirements; iterate development
that will include architecture, unit development and iterations of each phase. The iteration move
to system test to provide factory accepts test and move to site accepts testing. The process will
provide phased release of the software for production uses. The ability to provide the users with
software to use faster and get feedback on each phase will speed up the project and allow for the
user to get familiar with the software as each section is added.
The V-shape model is a sequential path process where each phase must be completed
before the next. Testing is developed early in the life cycle where the requirements begin in the
start of each phase with a testing plan.
A second option is the spiral model emphases on risk analysis. It has four phases:
planning, risk analysis, engineering and evaluation. This process is repeated as each phase is
introduced. The iterations is spiral based starting with planning phase, and the requirements are
assists and the risk are then processed and assets to the planning. The prototype is presented
after the risk assessment and the software is produced in the engineering phase where the testing
occurs and it ends the phase.

System Engineering Processes

Configuration Management
The configuration will for this project will have an introduction to new servers both
physical and virtual to the existing architectural. The servers will provide IIS web servers to host
the web application to allow customers the opportunity to sign onto the local governments portal
to apply for business licenses, building permits, file complaints and pay utility bills. The
interface it web based that gives logon access to employees and constituents this interface will be
required to protect the users information. The last configuration will be support of the

application. This will be a users interface that allows for them to view online videos, live chat,
Email and telephone contact.
Requirements Engineering
It is impossible to gather all the requirements needed for this project, so the
understanding that the information that is gathering will be done in phases iteration with
feedbacks. The requirements that are presented that is beyond the understanding of the team will
require the introduction of an outsource contractor expert on the requirements. The session to do
such will need the team to be diverse.
The system upgrade will need to provide servers with the following:
o
o
o
o
o
o

3.0 GHz processor

32 gig memory
5- 1TB Hot rack Hard drives
Windows server 2012
Microsoft SQL Server
Windows IIS 7.0 web server

Functional Analysis
The requirements will be grouped based on the business plan that is set forth by the
stakeholders. These documents will amend this document in version controls as each phase is
laid out, designed, developed, coded, tested, implemented and released. The versions will
function as living documents that will grow as each function is addressed and introduced into the
system.

Design Processes
The project will provide the clients with cloud services application that is served through
the server warehouse. Theses servers are to handle both the intra-net for designers and
developers as well as the internet service for local governments to run the application on.

Development Processes
Development process consists of IIS web servers running PHP server side scripting,
jQuery and JavaScript and MS Sql database. The hardware and servers will need to be cross
platform for Windows, UNIX and OS. The documentation from the developers, designer,
engineers, integrators, and coders will use Google Doc to provide live documents to collaborate
on.

Verification
It is up to the project managers to verify that the project objectives are being meet and
reviewed for insurance of acceptance from the feedback that is provided during each phase. This
will repeat over the life of the project.
Validation
The web application will be validated as the projects is phased and released in version
and control this will be done during each phase. When the project is completed it will go
through a beta test for a period of five weeks to provide the engineers with the assurance of the
system run status and reliability. When the application has completed the beta testing it will be
pushed out to customers to use.

Specialty Engineering
The attributes that are used in the evaluation of a system are feasibility, reliability, usability,
maintainability, producibility and disposability; although all of them are important the reason is
the ability to provide a user an easy to navigate system. The development of any system or
application that is not user friendly then most will complain about it and production will

diminish. The usability is important of the development of any application the directive is to
provide a productive environment that meets the business model for the client.
The usability is to encompass the guidelines for accessibility for disabilities in software
applications. This is evaluated in the project management design phase. The evaluation is to
focus on how easy the user can learn the product as well as how satisfied the user is. The actions
that facilitate the usability are accomplished in the interface design and interaction.

System Deployment
Site preparation
The site preparation for the deployment of the system is to be identified by the IT
manager, this provides the project manager with identifiers of the requirements that the system
may need to be addressed if they system is in need to be updated or changed. The deployment
system is required to have all of the windows updated, current firewall configuration, and antivirus software up to date. The webserver is current with security patches and up and running for
the acceptance of the web application software. The domain is registered and forwarded to the
correct server to accept request from clients. The database is installed on a separate server to
insure that the security of the server is not compromised by the webserver being attached to the
internet.

System installation
The application is to be installed on to the webserver IIS7. This process will require that
the domain that is registered and the DNS is configured to accept the internet request from both

the users and the customers. The application is to be tested to ensure that it is connected to the
database to insure that the users may login and or register to use the system.
The system is to be running and prepared for emergency events. The system need to have
a batter backup that allows the system to run for three hours to allow the data to run the backup.
The information needs to be accessible by an emergency server that is provided by Amazon E3
in the event that the servers are down beyond three hours.

System checkout
The IT manager is to run the system through the runs to insure that it is accepting request
and calls from the internet and intranet. The webserver is to be check for connection to the
switch, router and internet. The bandwidth is required to be at the maximum performance and
checked twice a day in the morning and then at the end of shift. The IT network technician is to
monitor the system and keep a log of the checks for the manger to review.

User training
The training staff is to provide the company with both onsite and web based training for
the employees. The training will consists of two eight hour onsite training that contains both
group training and individual training. The employees will be required to complete a mock run
of all the forms and procedures that the application provides within their job requirement. The
company will provide a select group of individuals that are to become the trainers. They will go
through the train the trainers program to provide training to the employees after the training team
leaves.
The users will have the ability to seen emails, or use the live chat to ask questions to
receive help. This will provide the user with a quick response to the user. The web application

has a built in help screen that have various videos that walks the user through different problems
as well as wiki that can be searched.

Product Support
Maintenance
The maintenance of the system is needed to be complete on a daily basis; this is to allow
for optimization of the system, so that the data is archived. The plan is to provide a set time after
midnight Eastern Standard Time for the system to go down for maintenance and backup. The
webserver is to provide a maintenance page so that it communicates with the users that the
system is down during this time. Maintenance is to be completed on every server daily and
monthly on the workstation.

Logistics support
The logistic process it to be handled by the purchasing manager via a request for the
product that is in need. The replacement of hardware that is required to be replaced in the result
of a disaster will come from an account that is limited to the IT administrator use of company
credit card with a purchase order explaining the location, name of hardware, hardware server
type, the cost and location from purchase to be emailed to the stakeholders and documented.
This is to be sent to the purchasing manager to code for accounting.

Disposal
The information that is used in the system is to be kept and not disposed of. The
information is requires to meet the state requirements for keeping records. The disposal of

information will only apply to the system testing information. This is to be removed before
going live with the system.

References
Brown, S., & Levine, R. (2011, January 02). Examples of a Project Management Budget.
Retrieved February 3, 2011, from www. brighthub.com:
http://www.brighthub.com/office/project-management/articles/61658.aspx
Cloud Computing. (2010, December 21). Retrieved September 21, 2013, from
www.techtarget.com: http://searchcloudcomputing.techtarget.com/definition/cloudcomputing
Elky, S. (2006, May 31). An Introduction to Information System Risk. Retrieved September 14,
2013, from www.sans.org: http://www.sans.org/readingroom/whitepapers/auditing/introduction-information-system-risk-management-1204?
show=introduction-information-system-risk-management-1204&cat=auditing
Joint Application Development and Rapid Application Development. (2008). Retrieved
November 24, 2013, from www.psu.edu:
http://www2.ds.psu.edu/AcademicAffairs/Classes/IST260W/topic03/topic_0112_06.html
Life Cycle Models in 15288. (2014). Retrieved April 20, 2014, from www.15288.com:
http://www.15288.com/stages.php
Meredith, J. R., & Mantel, S. J. (2009). Project Management. Hoboken: John Wiley & Son Inc.
Systems Engineering Applications Profiles Version 3. (2000, July). Retrieved from
www.incose.org: http://www.incose.org/ProductsPubs/pdf/techdata/SEAppsTC/SEApplicationsProfiles_2000-07.pdf
Systems Engineering for Intelligent Transportation Systems. (n.d.). Retrieved from
www.fhwa.dot.gov: http://ops.fhwa.dot.gov/publications/seitsguide/section4.htm

Systems Engineering Management Plan Template. (2014, April 10). Retrieved from
www.fhwa.dot.gov:
http://www.fhwa.dot.gov/cadiv/segb/views/document/sections/section8/8_4_2.cfm
SYSTEMS ENGINEERING PROFILES. (1998, August). Retrieved from www.isr.umd.edu:
http://www.isr.umd.edu/~austin/ense621.d/project99.html
Web Testing: Complete guide on testng web application. (2007). Retrieved November 4, 2011,
from www.SoftwareTestingHelp.com: http://www.softwaretestinghelp.com/webapplication-testing/
Web-Based Systems Vs. Server Based Systems. (2009, March 12). Retrieved April 14, 2011, from
ArticlesBase.com : http://www.articlesbase.com/software-articles/webbased-systems-vsserver-based-systems-813651.html