SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
SYSTEMS
ENGINEERING
PROJECT
LastUpdated:
August15,
2015
ThisdocumentprovidestheguidelinesandrequirementsfortheJohns
HopkinsUniversityWhitingSchoolofEngineeringSystemsEngineering
Project
V008_00
Guidelines
and
Requirements
Page1
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
TABLEOFCONTENTS
SYSTEMSENGINEERINGPROJECT.....................................................................................................................................1
TABLEOFCONTENTS........................................................................................................................................................2
MEMORANDUMFROMTHEVICEPROGRAMCHAIR........................................................................................................3
SYSTEMSENGINEERINGPROJECT-GuidelinesandRequirements...................................................................................6
1.0 SCOPEANDREQUIREMENTS..................................................................................................................................6
2.0 ORGANIZATION......................................................................................................................................................7
2.1 SelectionandApprovalofProject.................................................................................................................7
2.2 ApplicationofSystemsEngineering..............................................................................................................7
2.3 FinalReportandOralPresentation...............................................................................................................7
3.0 FACULTYGUIDANCE...............................................................................................................................................8
3.1 ProjectMentor..............................................................................................................................................8
4.0 SELECTIONANDAPPROVALOFPROJECT................................................................................................................9
4.1 SelectionoftheProjectSystem....................................................................................................................9
4.2 CriteriaforSuccessfulSystemProjects.........................................................................................................9
4.3 ProjectConcept...........................................................................................................................................12
4.4 ProjectProposal..........................................................................................................................................12
5.0 APPLICATIONOFSYSTEMSENGINEERING............................................................................................................15
5.1 RequirementsAnalysisandConceptofOperationsReports......................................................................15
5.2FunctionalAnalysisReport........................................................................................................................15
5.3 ConceptualDesign......................................................................................................................................16
5.4 TradeStudy.................................................................................................................................................16
5.5 TestPlan......................................................................................................................................................17
5.6 SystemSpecification(A-Spec).....................................................................................................................17
6.0 FINALREPORTANDPRESENTATION.....................................................................................................................18
6.1 FinalProjectReport....................................................................................................................................18
6.2 OralPresentationandCritique...................................................................................................................20
7.0 SCHEDULE.............................................................................................................................................................21
8.0 REQUIREMENTSFORONLINESTUDENTS.............................................................................................................22
9.0 GRADINGRUBRIC.................................................................................................................................................22
APPENDIXA-SelectionofProjectSystemTopics...........................................................................................................24
GeneralAttributes..........................................................................................................................................................24
WorkRelatedProjects....................................................................................................................................................24
CommunityRelatedProjects..........................................................................................................................................25
NewDeviceProjects.......................................................................................................................................................25
PersonalProjects............................................................................................................................................................26
RealityandOriginality.....................................................................................................................................................26
APPENDIXB-FrequentProjectSystemDeficiencies......................................................................................................27
V008_00
Page2
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
MEMORANDUMFROMTHEVICEPROGRAMCHAIR
August2015
To:
JHUSystemsEngineeringProjectStudents
From: Dr.DavidFlanigan,ViceProgramChair
SystemsEngineeringMasterofScienceDegreeProgram
[email protected]
Subject:SystemsEngineeringProject(645.800)GuidelinesandRequirements
NOTE:Thisrevisiontotheguidelinesiseffectiveimmediately.
Changesfromthepreviousversion:
1. CombinedProjectConceptandProposalintoonedocument.
2. MadetheRiskManagementReportmandatory.
3. MadetheTestandEvaluationReportmandatory.
The Systems Engineering Project represents the Capstone course in the Master of Science in Systems
Engineering. It is designed for you to (a) demonstrate that you can apply the "Systems Engineering
Viewpoint"and(b)exercisetheskillsandtoolsyouhavelearnedthroughouttheprogram.Itrequiresyou
toselectandcompleteacomplexanduniquesystemsengineeringprojectasanindividualstudent.Faculty
mentorsareavailabletoassiststudentsinselectinganddefininganappropriateproject.AnapprovedJHU
faculty member will serve as a mentor to guide you through the remainder of the project. The class
structureissimilartoanindependentstudyasitisself-pacedanddoesnothaveregularclasssessions.On
occasion,duringthesemester,amentormayannounceameetingofinterestedstudentstodiscusstheir
progress,answerquestionsandsharelessonslearned.Studentsenrolledinaconcentrationproject,803,
805, 806, 807, and 808 will have two mentors: an assigned concentration mentor and a system
engineeringmentorofyourchoice.
Sinceselectingasuitableprojectisoftentime-consuming,youshouldbegintheprocessaftercompletion
of the Systems Design and Integration course. You should plan to submit your Proposal during the
semesterimmediatelypriortoenrollingintheSystemsEngineering(SE)Projectcourse.Youshouldexpect
tospend150-250hoursofindependent,individualworktocompletetheproject,soweadvisethattheSE
Project course be the only course taken during the semester. The project schedule is self-paced, so a
strongcommitmentisrequiredtocompletetheprojectina24-weekperiod(theprocessbegins10-weeks
priortothestartofthesemester).Itisnotunusualthatanadditionalsemesterberequiredtocomplete
the course requirements. In these cases, an “Incomplete” grade can be requested to finish up the
V008_00
Page3
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
deliverables the following semester without an additional enrollment cost. A grade change fee will be
assessed.
Johns Hopkins University (JHU) has a rule that students are expected to complete their degree
requirementswithinfiveyears.Ifthereisanyconcerninthisregard,thestudentmustcontactDr.Flanigan
andprovideasignificantjustificationforanextensionofthefive-yearrule.
The most significant challenge of this project course is the need for students to remain committed to
completionoftheirprojectworkonaself-paced,independentbasis.Whilenormalworkandlifeconflicts
willoccur,attentionandfocusonmaintainingyourscheduleisessentialforsuccess.Thisdisciplineisan
excellentqualityforasystemsengineer.
Once approvals of the Proposal is given by your Project Instructor, there are several additional
deliverables:RequirementsAnalysisReport(RAR);ConceptofOperations(CONOPS)(RARandCONOPSare
MentorNote:YourConceptPaperandProposalshouldbecompletedandapprovedpriortothestart
oftheformalsemester.Itwillbeverydifficulttocompletetheprojectinonesemesterifyouhavenot
alreadycompletedthesetwodeliverables.
deliveredasoneproduct);FunctionalAnalysisReport(FAR);ConceptualDesignReport(CDR);TradeStudy
(TS); Risk Management Report (RMR); System Specification (A-Spec); Final Report (FR); and an Oral
Presentation(OP).
SeveralpriorstudentprojectreportsareavailableintheirentiretyonBlackboardtouseasexamplesand
guidesduringyourproject.YouarealsowelcometovisittheSEprojectlibraryattheJHUAppliedPhysics
Laboratory(APL)inLaurel,MarylandorattheSouthernMarylandHigherEducationCenternearPatuxent
River,Marylandtoviewcompletedprojects.PleasecallJacqueRowe,at443-778-8741(Baltimore)or240228-8741(Washington)foranappointmenttovisittheAPLlibrarybetween8:30AMand4:00PM.
Project communication and administration between the student and mentor shall be conducted via the
use of Blackboard. E-mail can be used for initial contact with the project instructor, the course
administratorandthementor(s)orusedinabackupmodeduringtheproject.
TheprimarymeansforinteractionbetweentheparticipantswouldbetheJHUsupportedBlackboardsite
(hereafter known as the SE Project website). Several of the SE courses have used the Internet in this
manner,soitislikelyfamiliartomoststudents.JHU’sintentistoprovideaccesstotheSEProjectwebsite
afewweeksafteryourenrollmentintheSystemsDesignandIntegrationcourse.Ifyoucannotaccessthe
V008_00
Page4
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
course in the website homepage after that time, request access to the SE Project website by providing
yourJHUID(alsoknownasyourJHEDID)[email protected]–shewillbeabletoaddyouto
thewebsite.Youwillneedtouse(orobtainfromtheEPwebsite)yourpasswordtousethesite.
To begin the process, the student initiates contact with a project mentor and through a series of draft
submissions, iteratively develops a Proposal (active mentors can be found on the course website. More
information about mentors can be found in 3.1 Project Mentor). Once the mentor approves the paper,
the student formally submits the paper on Blackboard and notifies his/her Project Instructor via e-mail
thatitisreadyforreview.Studentsshouldmaketheattempttoselectamentorandbegintheproposal
process prior to the semester they are registering for the project in order to maximize the chance of
successfulcompletion.
TheSEProjectwebsitecontainsseveralhelpfulaidsforyourprojectandwillserveasthemeansforyouto
communicateandsubmityourdeliverables.Therearetheseprojectguidelines,pointsofcontact,multiple
completedstudentprojects,andlinkstotoolsforyourpossibleuseduringtheproject(DOORS,CORE,MS
Project, etc.). The SE Project website will provide you with both correspondence and submission tools.
MoreinformationontheSEProjectwebsitecanbefoundwithinthesiteitself.Thesitecanserveasan
archive for your submissions, although it is prudent for you to maintain copies on your own computer
resources. General Internet help can be obtained from the JHU related help site. SE Project website
MentorNote:AlthoughsampleprojectsuploadedtoBlackboardwerechosenbasedontheircontent,
don't assume that every element of these projects is perfect. Students should review multiple
examplesanddetermineontheirownwhichcharacteristicstoapplytotheirownproject.
specificquestionscanbeaddressedtoChristian.Utara@[email protected].
Inordertocompleteyourprojectintimetomeetendofsemesterdeadlines,youwillneedtoschedule
yourOralPresentationattheJHUAppliedPhysicsLaboratorybeforethe“lastdayofclasses”dateofthe
semester. Please contact Ms. Rowe or your mentor to do so. Plan ahead, since this is a busy time to
schedulealltheparticipants.Notallstudentswillbeabletobriefinthelastweek.
V008_00
Page5
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
SYSTEMSENGINEERINGPROJECT-GuidelinesandRequirements
1.0
SCOPEANDREQUIREMENTS
This document defines the purpose, objectives and requirements for the Systems Engineering Project
(645.800, 803, 805, 806, 807, and 808; also known as SM4) that each Masters Degree in Systems
Engineeringcandidatemustcompletepriortograduation.
Theprimarypurposeoftheprojectistodemonstratethatthestudentunderstandsandcanapplysystems
engineering principles to a specific system. The project shall involve the application of the following
systemsengineeringactivities:
•
•
•
•
•
•
•
•
•
DefinitionofNeedsandObjectives
RequirementsAnalysisandConceptofOperations
FunctionalAnalysis
ConceptualDesign
Trade-OffStudies
RiskManagement
TestandEvaluation
SystemSpecification(A-Spec)
FinalReportandOralPresentation
Toservethispurpose,theSystemsEngineeringProjectshallbeproductoriented,(ratherthanaresearch
studydesignedtoincreasethebodyofknowledge).Theproductitselfshallbeinthenatureofa"system"
with definable functional subsystems; it will be referred to as the "Project System." The Project System
shall address a perceived, definable and practical need. It shall have sufficient scope and complexity to
requiresystemsengineering,includechallengingtechnicalandengineeringcomponents,beuniqueinthat
itisnotaduplicationofanexistingsuccessfulsystem,andhaveapotentialvaluebeyondtheinterestof
the student. See APPENDIX A - Selection of Project System Topics and APPENDIX B - Frequent Project
SystemDeficienciesformoreinformation.
A secondary purpose of the project is to provide the student with the experience of planning and
organizingasignificanttask,partitioningthetaskintoasetofsubtasksanddeliverables,establishingand
maintainingascheduleofeffort,anddeliveringwritten andoraldescriptionsofthework.Tomirrorthe
real world, this self-paced course provides the experiences of work, project, personal conflicts and
pressures.
V008_00
Page6
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
2.0
ORGANIZATION
Thesystemprojectcanbeorganizedintothreeprimaryareas:
2.1
SelectionandApprovalofProject
Activity:SelectionanddefinitionoftheProjectSystem,andapprovaloftheProjectProposal
Deliverables:ProjectProposal.ThisproductrequiresapprovalbytheMentorandtheProjectInstructor
viatheSEProjectwebsite.
Mentor Note: Although your Mentor will provide you guidance during the development of your
proposal,theProject Instructorapproves/disapprovesthesedocuments.Makesuretoleaveadequate
timeforbothMentorandInstructorreviews.
2.2
ApplicationofSystemsEngineering
Activity:Thedevelopmentoftheselected"system"throughtheapplicationofsystemsengineeringtasks.
Deliverables:ReportsonintermediatestudiestermedsimilartoCDRLs.Eachoftheseproductsrequires
approvalbyyourMentorviatheSEProjectwebsite.
MentorNote:TheSEProjectwebsite(Blackboard)providesasinglelocationforSystemsEngineering
Project materials, Student/Mentor/Instructor interaction, and documentation submittal/review.
Using Blackboard minimizes the possibility that data will be "lost in the shuffle." Refer to the SE
project website for office hours (if appropriate), typical review dates, and other communication
details.TheSEProjectwebsitedatabasewillbeusedbytheJHUMainOfficetoassessyourprogress.
2.3
FinalReportandOralPresentation
Activity: Assembly of all deliverables into a Final Report and Oral Presentation to the Mentor, Project
Instructorandpossibleotherinterestedparties.
Deliverables:WrittenFinalReportandOralPresentation,includingallprojectdeliverablesasappendices.
V008_00
Page7
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
3.0
FACULTYGUIDANCE
3.1
ProjectMentor
Members of the Systems Engineering faculty will be available to assist the student in the selection of a
suitable Project System and in the execution of the project. During the project selection and proposal
preparation, the student will be assisted by a designated project mentor. A comprehensive mentor list
canbefoundbothontheSEProjectwebsite.
Studentsplanningtheirprojectconceptshouldcontactanymentoroftheirchoicewiththeirprojectideas
or contact their Project Instructor directly for additional guidance. Students may select any Mentor
independentoftheirmaincampus.YourMentorwillassistyouintheselectionanddefinitionofasuitable
ProjectSystem.
Capstone Project students in a concentration area will have the student’s selected SE mentor and a
concentrationmentor.Theconcentrationprojectsareidenticaltothesystems800projects,exceptthe
system concept will focus on the concentration area. For example, an Information Assurance project
(645.806) would design a complete system but the design details would be on the security aspects of
thenetworks,processandcommunicationscomponentsofthesystem.
The faculty mentor will provide the student with advice and guidance on execution of the approved
project. After Proposal approval, the Mentor has approval authority, subject to oversight by the Project
Instructor,forallprojectreportsubmissions.Thestudentisstronglyencouragedtoseekinformationand
advicefromcolleaguesorauthoritieswithexpertiseinthedomainareaoftheproject.
Itisexpectedthatthestudentandmentorwillmaintaincommunicationsatleasteverytwoweeksduring
thecourseoftheproject.InteractionsshouldoccurprimarilyviaBlackboard,buttelephoneandin-person
sessionsarealsoappropriate.Itisthestudent'sresponsibilitytomaintaincontactandnotifythementor
ofanychangesduetotravelorotherconflicts.Alldocumentspreparedbythestudentshallbepostedto
Blackboard for review by their Mentor. It is expected that the student will be regularly developing and
postingdesignatedreportsformentorcommentonBlackboard.Thismaterialwilllatercomposesections
oftheFinalReport.Therewilllikelybeseveraliterationsforeachdeliverablebasedonfeedbackfromyour
Mentor.
V008_00
Page8
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
4.0
SELECTIONANDAPPROVALOFPROJECT
4.1
SelectionoftheProjectSystem
StudentsareencouragedtoselecttheirownProjectSystemorConcept.Ideally,theremaybeasuitable
subject associated with their job, place of employment or community. The project mentor will assist
students in the selection of the Project System. Previous Project System final reports are available to
stimulateconceptideasattheAPLorSMHEClibrariesorontheSEProjectwebsite.
4.2
CriteriaforSuccessfulSystemProjects
ScopeoftheProjectProduct
Asstatedabove,theproduct(oftheproject)shallitselfbea“system”whosedevelopmentinvolves
multiplesubsystemsandtechnicalissuesthatrequiresolutionstointerdisciplinarysystemproblems.
Theseconditionsarenecessarytowarranttheapplicationofsystemsengineeringratherthanofasingle
discipline.Forexample,itshouldnotconsistprimarilyoftheselectionandassemblyofcommercially
availablecomponentsorsoftware.Exclusivelysoftware-orientedsystemsmaybedifficulttomeetthe
projectobjectives.Thefunctionalityoftheconceptshouldnotbesimplyperformedbyamobile
application(app).StudentshouldthoroughlysearchtheInternetandpatentsdatabasestoverifythat
therearenotanyexistingcommercialsystemsavailablefortheirconcept.Theremustbetechnical
challengesrequiringsystemsengineeringtoachieveasuccessfulproduct(SeeSection8.0–Requirements
forOnlineStudents)
DomainKnowledge
Preferably, the student should already know about the proposed subject or be in a position to acquire
detailed knowledge from readily available sources (domain experts). To demonstrate the application of
systems engineering requires sufficient depth of understanding as to make it meaningful rather than
vague or very general. Projects, about which the student has little personal knowledge, and where
potential users may not be immediately available to the student, are generally difficult to carry out
becauseoftheextensiveresearchrequired.Ontheotherhand,iftheprojectiscloselyworkrelated,itwill
be necessary to demonstrate the student’s unique contributions and to avoid using existing work
generatedbycolleaguesorcontractors.Previousexperiencehasshownthatstudentswhoselectaworkrelatedprojectwilltendtofocusonthedesignandimplementationdetails,alongwiththisstakeholders,
whichisnottheintentofthisproject,andwillnotdemonstratethesystemsengineeringmethodintheir
deliverables.Indevelopingauniquesystem,thestudentwillbeexpectedtointervieworsurveyseveral
domainexpertstosolicitsystemsrequirementsandlatertovalidatethemduringtheprojectexecution.
V008_00
Page9
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
Mentor Note: It is expected that the student will be required to use a variety of documents and
referencesinsupportofthedevelopmentoftheirProjectSystem.Duetothenatureofthisproject,it
iscriticalthatallresourcesbeattributabletotheirsource.
MicrosoftWordhassomegoodbuiltinreferencingtoolsthatcanhelpyoutogetstarted.Ifyoudon'thave
MicrosoftWord,orifyouwouldliketomanuallyproduceyourreferences,besuretocapturethefollowing
information(ataminimum).
• Author(s)
• DateofPublication(ifavailable)-ifawebsitereference,includethedateitwasdownloaded
• TitleofPublication
• SourceofPublication(publisher,locationofpublisher,orwebsite)
• Iftakingadirectquote,includethepagenumberforthequote
APA,MLA,andChicagoformattingstylesareacceptableforthiscourse.
APA Examples
Inline Reference Example
(Annis, 2003, pp. 397-404)
End of Paper Reference Examples
Annis, D. B. (2003). A contextualist theory of epistemic justification. In P. K. Moser, & A. Vander Nat (Eds.),
Human knowledge: Classical and contemporary approaches (3rd ed., pp. 397-404). New York: Oxford
University Press. (Original work published 1978)
Flavin, C. (1998). The use of wind power should be increased. Charles P. Cozic (Ed.), Global Resources.
Greenhaven Press. Retrieved December 2, 2003 from website: http://include-website-name-here.
SeparationfromStudent'sJob
Iftheprojectisrelatedtothestudent'sjob,itshallbeclearlyidentifiedastheJHUSystemsEngineering
Project, and its accomplishment should not depend on any future changes in the job. Security and
proprietaryissuesshallbedealtwithbeforestarting.Contactyourworksupervisorandyourmentorifyou
have questions in this area. Several prior projects have classified origins or applications, but the project
environment,applicationdetails,customers,etc.canbecreativelydevisedtoconducttheprojectonan
unclassifiedbasis.Studentsareresponsibletoobtainingpublicreleaseofanyworkrelatedprojectifitis
needed.
V008_00
Page10
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
DemonstrableNeed
TheProjectSystemshallproduceorleadtoaproductthathasdemonstrablevaluetoanidentifiablerange
of"customers","owners"or"users"(specificindividualsshouldbenamedintheProposalandbetreated
as having this role). Current commercial or military Requests for Proposals may be considered, but the
student project shall not be redundant with an ongoing organization’s response. The Project System
shouldbe,inasense,potentiallymarketable.Itneedstobe“real”andviableinthemarketplace. Certain
commercial Project Systems may need to include some discussion of business planning factors to help
justifyfeasibility.TheProjectSystemshallnotbeofvalueonlytothestudent/developer—thatlacksthe
essential aspect of developing and analyzing requirements, i.e., the student cannot be the customer or
owner.FailingtomeetthisDemonstrableNeedcriterionraisesdoubtastothevalueofdevelopingsucha
system.
Feasibility
IftheproposedProjectSystemrepresentsasignificanttechnicaladvance,itshallbeshowntobefeasible.
Thereshouldbeatleastoneimplementationoftheconceptthatdoesnotrequireinventionofsomething
entirelynewtosatisfytherequirements.FailingtheFeasiblitycriterionmakestheprojectunrealistic.The
ProjectSystemrequirementsareexpectedtobequantitativeasmuchaspossible.Hence,realsubsystem
designspecificationsshouldresultfromtheresearchandtradestudies.
Complexity
The Project System should consist of several different subsystems, so that it presents system problems
that could not be solved by a single design specialist. In the case of a software-centric system, the
application domain shall be sufficiently complex as to require a system approach to its design (the
required hardware subsystems shall not be neglected). Ideal systems will have both hardware and
softwarecomponents.Ontheotherhand,theprojectshouldnotbesocomplexastoexceedthescopeof
what can be accomplished in one (or two) semesters for an academic system project course. Early in
developing the system concept, the student can evaluate complexity by sketching out a systems
conceptualblockdiagramandnotingthenumberofinternalandexternalinterfaces.
Mentor Note: The requirement to develop a system conceptual block diagram in the proposal helps
thestudentvisualizeatleastonefeasiblesolutiontomeettheneed.Althoughthestudentisexpected
to deviate significantly from this initial "system concept", thinking through the Project System as a
wholeminimizesthepossibilitythatasolutionwillbeunattainable.Developingthesystemconceptual
blockdiagramalsoprovidesa"firstlook"atthecomplexityofatleastonepotentialsolution.
V008_00
Page11
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
SystemFocusandScope
Theprojectshallbefocusedonsystemsengineeringratherthanoncomponentdesign.Projectsthatfocus
onthedesignofadeviceorasoftwareprogramthataccomplishesarelativelylimitedfunctionarelikely
tobetoosimplistictorequire"systems"thinking.Adetailedprocessisnotitselfasystemproduct.Ifan
engineering or software specialist can accomplish the concept, it may not present opportunities to
exercisesystemsengineeringskills.Writingacomputerprogramorcombiningasetofsoftwarealgorithms
shouldnotbesignificantelementsofthework.
Specificity
While the focus of the project must not be on design details, neither can it be on generalities. The
application of systems engineering methods should be on realistic engineering (and sometimes
programmatic)issues.ThesubsystemsandcomponentsoftheProjectSystemneedtohaveaquantitative
foundation.Forexample,inconductingatradestudy,thecriterianeedtobetraceabletorequirements,
objective,andthechoicestechnicallycomparableandthejudgmentsmadeonnumericalfactorsasmuch
aspossible.
UnsatisfactoryProjects
Some examples of unsatisfactory proposed System Projects have included systems requiring only the
assembly of commercially available-standard components that could be assembled by a technician;
integration of Commercial-Off-The-Shelf components; database systems for storing and accessing data
that could be designed by a database specialist or adapted from a commercial product; and in general,
componentdevelopmentswithintheknowledgedomainofasinglediscipline(SeeAPPENDIXB-Frequent
ProjectSystemDeficiencies).SystemsProjectsthatarenowcommoninthemarketplaceshouldalsobe
avoided,e.g.,smarthomes,autonomousautomobiles,lostchildren-pets-cars,groceryshopping,etc.
4.3
ProjectConcept
Theprojectconceptpaperisnolongerrequired.IthasbeenmergedintotheProjectProposal.
4.4
ProjectProposal
The project proposal is a detailed description of the proposed system, a full and formal
statement/demonstration of the plan for accomplishing the project. It shall describe the objectives, the
preliminary view of the system design, the systems engineering method of approach, the project work
statement, the project work breakdown and schedule and the risk management plan. The Proposal is
iterativelydevelopedwithfeedbackfromthestudent’smentor.Thestudentscheduleshouldbepresented
in Microsoft Project (or equivalent) format. The organization of the Proposal is described below. While
awaitingcommentsandapprovalfromtheProjectInstructor,thestudentshouldinitiatetheprojectwork.
V008_00
Page12
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
ProposalFormat
SECTION1:SystemIntroduction
Thissectionincludesthenameofthesystem,thestudentname,thementorname,andabriefstudent
biography.
SECTION2:NeedfortheSystem
Describethecapabilityneedorgapofexistingsystems.Includethereferencestoresearchonthetopicto
demonstrate that the student has a clear grasp of the domain problem. Describe the proposed system
conceptinordertoaddressthisneed/gap.Justifytheimportanceofrequiringthissystemtoaddressthis
gap.
SECTION3:SystemArchitecture/DescriptionofSystem
Apreliminarydiscussionandillustrationoftheproposedsystemshallbepresentedtoprovideinsightinto
the possible subsystem components and interfaces and their functionality. The student shall include an
initial/preliminary conceptual block diagram and context diagram for the system (see Feasibility and
Complexityabove).Duringthecourseoftheproject,thesystemfunctionsand/ordesignareexpectedto
changeasthesystemsengineeringprocessisapplied.Ataminimum,thissectionshouldinclude:
•
•
TheSystemContextDiagram(thewhiteboxviewofthesystem)
o Intendedstakeholdersthatwouldinteractwiththesystem.
o Intendeddomainenvironmentthatthesystemwouldoperatein.
o Externalsystems/organizationsthatthesystemwouldinteractwith.
SystemConceptualBlockDiagram.Thisdiagramwillencompassthesystemcomponentsthatthe
projectisexpectedtoinclude.Thisdiagramshouldbealignedwiththesystemcontextdiagram.
SECTION4:ProjectBackground
Identify2-4stakeholdersthatyouintendtointerfacewithduringyourprojectandtheirbackgroundthat
willberelevanttoyourproject.Developaworkbreakdownstructure(WBS)andidentifythetimeframeof
themajordeliverablestoincludethefinalpresentationdate(milestonesandschedules).Identify4-6risks
thatyouanticipatetoconsiderandaddressduringtheproject,ensuretheserisksareunderyourproject
control.
WBS
This section identifies specific tasks (20 or more) to be performed in the project. These tasks shall be
grouped in a Work Breakdown Structure (WBS) showing how they relate to one another. The general
purpose of each task shall be indicated. For each task the estimated number of hours of effort to be
requiredbythestudentshallbelistedtodemonstratethattheworkhasbeencarefullyplannedandthat
thetotalscopeoftheprojectisappropriate.Tasksshallbeproduct-oriented.EachWBSelementshallbe
V008_00
Page13
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
brokendowntoincrementsnogreaterthan20hours(10hourspreferred).UseofMicrosoftProject(or
similartool,suchasOpenProject)fortheWBSandscheduleisexpected.
MilestonesandSchedules
The Milestones section shall identify the key dates or events marking project delivery dates and major
reviewpoints.Thescheduleshallidentifytheestimatedstart/completiondatesforeachmajortask.Both
the milestones and the schedule shall be traced to the Work Breakdown Structure. Contingencies and
backupplansshouldbeevidentintheschedule.
MentorNote:Don’tconsidertheWBS,milestones,andscheduletobepurelyacademicdeliverables.The
WBS,alongwithyourmilestonesandschedule,shouldprovideasoundfoundationforyoutoworkfrom
throughoutthesemester.StudentsthatdevelopacomprehensiveWBS/schedule,typicallydoabetterjob
managingtheir time.Thesestudentsactuallyreferback to theirplanthroughoutthe semestertokeep
themontrack.
RiskManagement/InitialRiskAssessment
Themethodthestudentwillusetoidentify,monitor,mitigateandmanageriskduringtheprojectshallbe
discussedandillustrated.Thefocusshouldbeontechnicalrisksforthesystemandstudentprojectrisks,
notnormalprogrammaticrisksfacedbyeveryproject.SeethediscussionintheabovesectionIdentify2-4
stakeholdersthatyouintendtointerfacewithduringyourprojectandtheirbackgroundthatwillbe
relevanttoyourproject.Developaworkbreakdownstructure(WBS)andidentifythetimeframeofthe
majordeliverablestoincludethefinalpresentationdate(milestonesandschedules).Identify4-6risksthat
youanticipatetoconsiderandaddressduringtheproject,ensuretheserisksareunderyourproject
control.IntheProposal,aninitialsetofrisksshallbeincludedinatable.Ariskcubeandwaterfallchart
shallbeprovidedforoneofthetechnicalrisksidentified.
SECTION5:SystemsEngineeringJustification
Whywouldsystemsengineeringberequiredfortheproject(e.g.whatmakesyourprojectwarranta
systemsengineeringapproach)?List3scenariosthatwoulddescribeyoursystemoperationsand
interactionsthatyouwouldengageyourstakeholders(thisistogetyouthinkingaboutthedifferentways
yoursystemwilloperate).ListthetopfiveMeasuresofEffectiveness(MOE)thatcanmeasureyour
systemperformance.Listtheanalyticaltoolsandtechniquesyouwilluseduringtheprojecttoassessyour
systemperformance.
V008_00
Page14
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
5.0
APPLICATIONOFSYSTEMSENGINEERING
The second, and major, portion of the Project course is devoted to the development of the selected
systeminaccordancewiththeapprovedProjectProposal.Inthisportionofthecourse,thestudentwill
prepare several reports (CDRLs): Requirements Analysis / Concept of Operations, Functional Analysis,
Conceptual Design, one Trade Study, Test Plan, and a System Specification (A-Spec). These artifacts will
becomepartofthewrittenFinalReport(asappendices)alongwiththeProposal,otherrelevantdata,and
conclusionsandrecommendations.Thestudentshouldcontinuallyupdate/maintaintheWorkBreakdown
Structure,ScheduleandRiskManagementPlanastheyprogressthroughouttheproject.Thecontentsof
thesereportsaredescribedbrieflybelow.
5.1
RequirementsAnalysisandConceptofOperationsReports
The development of a new "system" has to be based on a well-formulated set of requirements derived
from an analysis of operational needs. Both originating and derived requirements shall be included.
Typically, a system project would have 150-200 total requirements. The Requirements Analysis Report
should describe the required operational outcomes that have been extracted from the Needs Analysis
(often derived from a Mission Needs Statement), and the key system performance requirements (often
called Key Performance Parameters) needed to realize the operational outcomes. The reasoning behind
each system requirement should be stated. Each requirement shall be labeled or numbered to
demonstratetraceabilitythroughouttheproject.Ultimately,therequirementswillbetracedtofunctions,
components, trade study criteria, subsystem specifications and validation methods. To the extent
possible, the requirements should be quantifiable, e.g., have numerical parameters listed to show the
rangeorscoperequiredfortherequirement.Thereportshallalsostatehowtheaccomplishmentofeach
major requirement would be verified. The integrated report incorporates the Concept of Operations
(CONOPS)withdiagrams,includingoneormorescenariosorusecasesillustratingthesystemfunctioning
initsoperationalenvironment.Dependingontheproject,thestudentmayconsidertheuseofatoolsuch
asDOORStomanagetherequirementsinformation.Typically,thisisthemostchallengingreportasthisis
thefirstreportoftheproject.Takespecificcaretodescribetheneededcapabilitiesthatcanbegathered
fromyourstakeholdersandcanbedevelopedfromyourscenarios/usecases.Thefunctionalitythatis
requiredintheusecasescanaidyouindevelopingthefunctionalarchitectureintheFAR.
5.2FunctionalAnalysisReport
Prior to initiating Functional Analysis, the requirements must be well defined and validated (preferably
with the customer/user). As the Functional Analysis begins, the requirements are translated into the
functionsthatmustbeperformed.Thesefunctionsareultimatelytranslatedorallocatedintosubsystems.
Onemustvisualizethetypeofsystemneededtomeettherequirementsandthesubsystemfunctionsthat
will implement the projected objectives. Various attributes of the system such as System States and
Modes,SystemFunctions,andFunctionalInterfacesaredefined.Thestatesandmodesconsiderationswill
help to ferret out details of interfaces and time-varying requirements. At a minimum, this artifact shall
V008_00
Page15
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
include a functional context diagram, functional flow and or functional block diagrams (at least two to
three levels), N2 diagrams (as appropriate), and traceability back to requirements (use of a table is
helpful).Dependingontheproject,thestudentmayconsidertheuseofatoolsuchasCOREtomanage
thefunctionalarchitectureandtraceability.
5.3
ConceptualDesign
FunctionalAnalysisnormallydefinesthefunctionsthatthesystemneedstoperforminordertomeetthe
performance requirements. A vision of how the functional architecture might be realized by hardware
andsoftwarecomponentsconstitutesaConceptualDesignoftheproposedsystem.Interfacesshallalso
bedefinedandoptionallyanInterfaceControlDocumentcanbegenerated.Aphysicalcontextdiagram,
physical block diagrams and allocation diagrams are typical products. The conceptual design shall also
includetraceabilitytofunctionsandrequirements(asappropriate).Inmostinstances,physicalinterfaces
should also be traced back to functional interfaces/interactions, captured during Functional Analysis.
Dependingontheproject,thestudentmayconsidertheuseofatoolsuchasCOREtomanagethephysical
architectureandtraceability.
5.4
TradeStudy
The systems engineering method uses trade-off analysis or analysis of alternatives as the means for
makingsignificanttechnicalandprogramdecisionsandinmitigatingtechnicalriskintheproductdesign.
IntheProject,thereshouldbeanumberofinformaltradestudies,ofwhichatoneshallbecarriedoutand
Mentor Note: Before you start developing your formal trade study, review your notes from class. You
shouldalreadyhaveastep-by-stepprocesstoperformatradestudyinhand.Afewhelpfulhints:
(1) Identifyyourrequirementsrelatedtoyourtradestudyupfront.
(2) Makesuretotraceeachselectioncriteriontorequirements,orprovideajustification/rationale
foritsuse.
(3) Ifyoudon'thaveanobjectiveweightingmethodinplace,usethepair-wisecomparisonmethod.
(4) Watchyoursignificantdigits!
reportedindetail.Althoughnotexplicitlyrequired,capturingtheresultsofyourinformaltradestudiesis
highlyencouraged.Thehierarchyofanalysesofalternativesincludesearlyconsiderationofapproachesto
top-leveldesigntoastudyofalternativesfordetailedsubcomponents.Fortheformalstudy,itisbestto
focusonthosesystemcomponentswherespecificationsandquantitativeinformationexiststoadequately
assessthetradespace.Inreportingthetradestudy,itisnecessarynotonlytodescribethetechnicalor
component alternatives considered, the quantitative selection criteria, their relative weighting and
scoring;buttherationaleforeachoftheseselections,assignmentsandscoringshallalsobedocumented.
V008_00
Page16
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
Thus,thereasonforselectingeachofthealternativesolutionstobeconsideredandeachcriterionshallbe
stated and traced to requirements. Weights assigned to criteria shall be justified, as well as the relative
scores given each alternative for each criterion. Finally, a sensitivity analysis shall be performed. The
significance of the results shall be discussed in the light of that analysis. In conducting the sensitivity
analysis it is helpful to successively zero-out each of the criteria to identify any possible bias in the
analysis.Thereareanumberoftoolsthatcouldbeusedforthiseffort.Ifatoolisused,thestudentshould
discussandthoroughlyunderstandtheinput,parameterspaceandoutputofthetools.
5.5
TestPlan
The test plan describes a selected portion of your system capability and develops a plan for which to
evaluate your system’s performance. As the project is largely in the conceptual design phase, it is not
intended to dive deeply in the test environment and details, but to facilitate consideration of the test
portionofthesystemsengineeringmethod.Thetestplanshouldincludethepertinentrequirementsthat
willbeincludedinthetest,testenvironment,equipmentthatwouldbeneededtomonitorandanalyze
thetest,testsubjects/expertisetoconductandanalyzethetest,desiredresultstodetermineifthetest
wassuccessful,andthemetricsintendedtobecollected.
5.6
SystemSpecification(A-Spec)
Thesystemspecificationembodiesthefunctionalrequirementstoberealizedbytheimplementationof
theconceptualdesignintohardwareandsoftwaresoastomeetthesystemoperationalrequirements.It
isnormallyakeyproductofthesystemconceptualdesignphase.Itwillvaryfromtheinitialrequirements
by revisions made during the project and the outcomes of previous artifacts. The specification shall be
written in a formal structure, showing traceability to the requirements, covering system definition,
requiredquantitativecharacteristics,supportrequirements,andanyspecialrequirementssuchassafety
andhumaninterfaces.Thestudentshallalsoinclude(asappropriate)anyconcernsthedesignermayneed
totakeintoaccount,suchasincompleteanalysis,unstablerequirements,businessortechnologyfactors
thatwentunaddressedandareasofdesignflexibilitywithintherequirementsenvelope.Asappropriate,
thestudentcanprovidespecialinstructionstothesystemdesigners/developers.Thesystemspecification
shouldincluderequirementsmetrics.Ataminimum,thereportshallinclude:
a)
b)
c)
d)
#ofinitialrequirements(fromRequirementsAnalysisReport)
#offinalrequirements(fromA-Spec/SystemSpec)
#/%ofqualitativerequirements
#/%ofquantitativerequirements
V008_00
Page17
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
6.0 FINALREPORTANDPRESENTATION
The culmination of the Project System is the submission of a formal written Final Report and an Oral
Presentationdescribingthestudent'sworkontheproject.
6.1
FinalProjectReport
The Final Report should consist mainly of an assembly of the Concept/Proposal and reports submitted
during system development, with introductory and concluding sections to put all of the parts into a
coherentcontext.TheProposalandreportspreviouslysubmitteddonothavetoberewritten.Thereport
shallbeincludedinthefinaldeliverable.ThesuggestedorganizationoftheFinalReportisasfollows:
TableofContents
ProjectObjectiveandApproach
Thissectionshallincludeasummarystatementdescribingthepurposeandgeneraldescriptionofthe
ProjectSystem.
SignificanceandScopeoftheWork
Thissectionshallincludethestudent'sperceptionofthesignificanceoftheworkfromtheperspectiveof
theproductsandresultsproducedbytheproject.
ProjectProposal
ThissectionshallcaptureabriefsummaryoftheprocessusedtodeveloptheProposal.Itshallreferto
theappendixthatcapturestheactualdocument.
RequirementsAnalysisandConceptofOperationsReports
ThissectionshallcaptureabriefsummaryoftheprocessusedtodeveloptheRequirementsAnalysis
Report.Itshallrefertotheappendixthatcapturestheactualdocument.
FunctionalAnalysisReport
ThissectionshallcaptureabriefsummaryoftheprocessusedtodeveloptheFunctionalAnalysisReport.
Itshallrefertotheappendixthatcapturestheactualdocument.
ConceptualDesignReport
ThissectionshallcaptureabriefsummaryoftheprocessusedtodeveloptheConceptualDesignReport.
Itshallrefertotheappendixthatcapturestheactualdocument.
TradeStudyReport
ThissectionshallcaptureabriefsummaryoftheprocessusedtodeveloptheTradeStudy.Itshallreferto
theappendixthatcapturestheactualdocument.
V008_00
Page18
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
RiskManagementReport
Thissectionshallcaptureabriefsummaryoftheprocessusedtomanagerisksthroughoutthesemester.
Itshallrefertotheappendixthatcapturestheactualdocumentationrelatedtorisk.
TestPlan
Thissectionshallcaptureabriefsummaryofthetestplanandtheportionofthesystemcapabilitythat
willbeevaluated.Itshallrefertotheappendixthatcapturestheactualdocument.
A-SpecificationReport
ThissectionshallcaptureabriefsummaryoftheprocessusedtodeveloptheA-Spec.Itshallrefertothe
MentorNote:Sinceyouwillberequiredto assess planned versus actual task/schedule performance
on your project, it is critical that you establish a method to track your progress (both in hours and
dates)throughoutthesemester.Makesuretokeepyourmetricsupdatedthroughoutthesemester!
appendixthatcapturestheactualdocument.
ScheduleAssessment
MentorNote:Asonemightexpect,youwill"learnlessons"throughoutthesemester.Maintainalog
of these lessons learned. It's much easier to copy/paste from your lessons learned log than it is to
recalltheselessonsattheendofthesemester.
Thissectionshallcomparetheplannedversusactualtask(hours)andschedule(dates)metrics.Any
significantdeviation(s)fromtheplannedvaluesshallbedocumented.
LessonsLearned
Thissectionshallcaptureobservations/lessonslearnedfromthestudent'sperspectiveduringexecutionof
theproject.
EvaluationandNextSteps
Thissectionshallprovideconclusionsonthevalueoftheprojecttothestudentaswellastotheintended
users.Includeadiscussionofanypossiblefollow-onactivities,plansorpotentialtowardsystem
realization.
V008_00
Page19
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
Recommendations
Thissectionshallincludethestudent'ssuggestionsonhowthevalueoftheSystemProjectcoursemight
beimproved.
Appendices
Afullcompilationoftheartifactsproducedinsupportofthisproject,includingtheoralpresentation
materials.
6.2
OralPresentationandCritique
In addition to the written Final Report, the student will give an Oral Presentation using summary
viewgraphs.Thispresentationisexpectedtolastaboutoneandonehalfhours,includingquestionsand
answers. The presentation should include 15 to 30 viewgraphs and the student should be prepared to
discuss the project with the reviewers. Any special exhibits or products should also be provided. The
examiners will generally include the Course Instructor, Program Vice-Chair and Project Mentor. Of
particularinterestisadiscussionoflessonslearnedfromtheproject.
Public students shall provide two notebooks and two CDs of ALL the CDRLS, including the Oral
Presentation,totheMentorandtheProjectInstructor.Publicstudentsshallalsouploadafinalversionof
theirdeliverablestoBlackboardbythedateofthescheduledpresentation.
OnlinestudentsshalluploadallfinalmaterialstotheBlackboardsitenolaterthan48-hoursinadvanceof
theirscheduledonlinepresentation.
V008_00
Page20
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
7.0
SCHEDULE
To complete the project by the end of a scheduled semester, it is necessary to have the subject of the
workwellinmindafewmonthspriorthestartofthecourse.Itisrecommendedthatthefirstpartofthe
work - Selection and Approval of Project System – through generation, review and approval of Concept
and Proposal Papers, begin the semester prior to course enrollment such that a full semester will be
available to do the bulk of the work. Since the project is self-paced and other priorities sometimes
intervene, only about 30% of students complete the work in the following notionaloverallschedule. Be
realisticbutworkhardtobecommittedtocompletethecourseandyourdegreerequirementsinoneto
twosemesters.Thefollowingisanotionaloverallschedule:
Week
Activity
EnrolledinSystems
Design&Integration
GainaccesstotheSEProjectWebsite
EnrolledinSystems
Test&Evaluation
EnrollinProjectInstructor&MentorGroups
-10
Exploresubjectsforproject
-5
Submitconceptforproject
-2
Submitproposalforproject
0
EnrollandstartsemesterforSystemsProjectCourse
1
CoordinateplanswithMentor
3
SubmitRequirementsAnalysis/CONOPSReports
4
SubmitFunctionalAnalysisReport
6
SubmitTradeStudyReport
8
SubmitConceptualDesignReport
10
SubmitTestPlan
11
SubmitA-SpecificationReport
12
SubmitDraftFinalReport
14
DeliverFinalReportandOralPresentation
V008_00
Page21
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
8.0
REQUIREMENTSFORONLINESTUDENTS
OnlinestudentswilluseBlackboardastheirprimarymechanismforinteractingwiththeirmentors.In
addition,studentsandmentorscanusetheAdobeConnecttoolasamechanismforreal-timeinteraction.
AllonlinestudentswillperformtheirfinaloralpresentationviaAdobeConnect.Therefore,online
studentsandtheirmentorsarerequiredtohave,asaminimum,acomputerheadset(headphonesand
microphone)andacomputervideocamera.Priortotheirfinalpresentation,studentsshouldtesttheir
computerwithAdobeConnecttopreventanylastminuteproblems.AnAdobeConnectsessionhasbeen
exclusivelysetupforthispurpose.Thelinktothissessionisincludedhere:
http://connect.johnshopkins.edu/sm4_test/
9.0
GRADINGRUBRIC
ThefocusonstudentattentionintheSystemProjectcourseshouldbeondemonstratingyourSE
knowledgeandskills.The“journey”isthemostimportantaspectofthisexperience.Nevertheless,after
thecompletionoftheOralPresentation,theUniversityrequiresthatagradebegivenforthestudent
performance.Thecourseinstructorandthementorwillassignagradebasedonthestudentbodyofwork
andthelevelofunderstandofsystemsengineeringdemonstratedduringtheoralpresentation.The
thinkingandinputfortheassignedgradeisbasedonthetablefoundonthenextpage:
V008_00
Page22
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
V008_00
Page23
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
APPENDIXA-SelectionofProjectSystemTopics
GeneralAttributes
AsstatedintheinstructionsfortheSystemsEngineeringProject,thesubjectselectedmustbecapableof
demonstrating the student’s ability to apply the methods of systems engineering learned during the
curriculumtoapracticalproblem.Thesemethodsinclude:
RequirementsAnalysisandConceptofOperations
FunctionalAnalysis
ConceptualDesign
TradeStudies
RiskManagement
TestandEvaluation
A-Specification
Inordertopermittheapplicationofsystemsengineeringprinciples,thesubjectitselfshall:
(1) beasystem-likeproduct
(2) havepotentialuserswhoneedsuchaproduct
(3) befeasiblewithexistingtechnology
(4) involverisksandtechnicalchallengesinitsaccomplishment
WorkRelatedProjects
Studentsareencouragedtoselectaprojectthatisrelatedtotheirworkwhencircumstancespermit.This
category represents the majority of system projects carried out to date. In a work-related project, the
studenthasaccesstoinformationconcerningtheuserenvironment,needs,opportunities,constraintsand
otherimportantdomainknowledge.Sometimes,suchprojectsalsoprovideanopportunitytocontribute
tothestudent’sworkplace.
V008_00
Page24
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
Examples:
(1) ConceptualDesignofaSonarSelf-NoiseFieldSystem
(2) AdvancedPortShipProtectionSystem
(3) LightingProtectionforanAntennaRange
C AUTION:Thereshallbeacleardistinctionbetweenthestudent’sworkplaceprojectandtheJHUproject.
TheexecutionoftheJHUprojectmustnotdependontheprogressorstatusoftheworkplaceproject.The
work conducted shall be that of the student. Also, the JHU project shall not depend on classified or
proprietaryinformationwhichwouldrestrictsubmissionofprojectreports.
CommunityRelatedProjects
Anumberofinterestingprojectshavebeenbasedoncommunityneedsandsuchprojectsusuallyprovide
ampleaccesstousersandotherdomainknowledge.However,therequirementthattheproblemmustbe
“system-like” narrows the opportunities to special cases, which require the application of systems
engineering.
Examples:
(1) SystemsfortheDevelopmentofanadvancedSchoolLocalAreaNetwork
(2) Management System for the Soccer Association of Howard County (teams, coaches, referees,
schedules,equipment,tournaments,etc.)
(3) Remodelingalargechurch(lighting,acoustics,choir,buildingcosts,etc.)
NewDeviceProjects
Somestudentshaveanideaofadevice(smallsystem)thattheybelievemightbemarketable.
Examples:
(1) AutomatingtheAnalysisandDataStorageofNeurotransmitterTests
(2) ATactileDisplayforBlindComputerUsers
(3) TransitInformationDisplayDevice
(4) FisheriesScientificComputerSystem
(5) AutomatedPanelAssemblyDeviceforaRadarApplication
V008_00
Page25
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
C AUTION:Thedeviceshallbesufficientlycomplexforapplicationofsystemsengineering.Thedeviceshall
be technically feasible and affordable and there must be a credible community of potential users. The
studentmusthaveadequateknowledgeofthetechnologyandpotentialofthedevice.
PersonalProjects
Inveryrarecases,projectshavebeenbasedonpersonalneedsbuttheyarenotrecommended.Asinthe
caseofwork-relatedprojects,theyhavetheadvantageofdomainknowledge.TobesuitableforaProject
System they need to have sufficient system-like scope to demonstrate systems engineering principles.
Thestudent(andfamily)shallnotbethesolecustomer–theresultsmustbeofvaluetoacommunityof
potentialusers.
Examples:
SailboatSysteminPreparationforCircumnavigation
OfficialClockforHighSchoolGames
RealityandOriginality
Except in special cases, the proposed Project System shall be real and the student’s approach shall be
original. Where the student wishes to deviate from reality for security or other reasons, or choose a
problemthathasbeenaddressedpreviously,acaseshouldbemadeandapprovalobtainedtopursuethe
approach.Inallcases,theprojectshallbewhollytheworkofthestudent,andanydeviationsshallbefully
realistic.
V008_00
Page26
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
APPENDIXB-FrequentProjectSystemDeficiencies
The following paragraphs list common deficiencies in selecting subjects for the Project System and
carrying it through to completion. Such cases lead to extensive resubmissions, resulting in delay of
graduationofstudentsforwhomthisistheirfinalcourse.Tomakegooduseofpastexperience,students
should review their project concepts against the cases described below. Project Mentors should also
considertheseexampleswhenexaminingstudentconceptsandproposals.
1. Inadequatesystemproduct
Projectproductnotclearlydefined;notsuitabletoillustrateapplicationofSEprinciples
Producttoosimple,and/orsolutiontooobvioustorequireSEapproach
Projectfocusesentirelyonaminorcomponentofasystem
2. Projectoverlyambitious
Projecttooambitioustobeaccomplishedwithinareasonabletimeandeffort
Systemverylargeand/orcomplex
Proposaloftreatmentoverlydetailed
3. Insufficientknowledgebase
Insufficientavailableinformationonprojectcharacteristics
Projectisnewideawithoutpriorexperienceorknowledgebase
Studenthaslimitedpersonalknowledgeofprojectrequirementsand/ortechnology
Excessiverelianceoninterviewstoobtainknowledge
4. Overemphasisonproductdesign
Emphasisonproductdesignratherthansystemsengineering
Projectinvolveswritingacomputerprogram
5. Toocloselytiedtostudent'sworkproject
Productidenticaltopartofstudent'scurrentjob
Projectmaybeadverselyaffectedbychangesinscheduleorcontentofjob
ConfusionbetweenobjectivesofJHUprojectandcompanyobjectives
Securityorproprietarycomplications
V008_00
Page27
SYSTEMSENGINEERINGPROJECT
GUIDELINES&REQUIREMENTS
LastUpdated:
August15,2015
6. Projectonlyofpotentialvaluetostudentorfamily
Studentissole“customer”forproject
Requirementssolelyprovidedbystudent
7. Inadequatetreatmentofsubject
Studentunderestimatesthethoroughnessofplanning,executionandwritingrequired
ApplicationoftoofewSEprinciples
Reasoninginapplyingprinciplesnotexplained
Write-upsarecursory,superficial
Keyitemsrequiredinprojectspecificationsomittedorslighted
8. Inadequateexecutionofproject
PoorProposalplan
Failuretofollowplan
Inadequatecommunicationwithmentor
V008_00
Page28