IEEESoftwareRequirementsSpecificationTemplate.docx
- 文档编号:24603918
- 上传时间:2023-05-29
- 格式:DOCX
- 页数:7
- 大小:16.80KB
IEEESoftwareRequirementsSpecificationTemplate.docx
《IEEESoftwareRequirementsSpecificationTemplate.docx》由会员分享,可在线阅读,更多相关《IEEESoftwareRequirementsSpecificationTemplate.docx(7页珍藏版)》请在冰豆网上搜索。
IEEESoftwareRequirementsSpecificationTemplate
IEEESoftwareRequirementsSpecificationTemplate
PlansProposal
for
OSEKOperatingSystem
Development
PreparedbyInfiniteteam
2006/10/13
PlansProposalforOSEKOSDevelopmentPageii
TableofContents
TableofContents..........................................................................................................................iiRevisionHistory...........................................................................................................................iii1.Introduction..............................................................................................................................1Reference.................................................................................................................................................12.Context......................................................................................................................................22.1Projectoverview..........................................................................................................................22.2Teamname..................................................................................................................................22.3Teammembers............................................................................................................................22.4ProjectDimensionofThisProposal............................................................................................23.Approaches...............................................................................................................................33.1Methods.......................................................................................................................................33.2Techniques...................................................................................................................................33.3Strategies.....................................................................................................................................33.4Artifacts.......................................................................................................................................43.5References...................................................................................................................................44.Analysis.....................................................................................................................................44.1ApproachVerificationandValidation........................................................................................44.2Artifacts.......................................................................................................................................44.3References...................................................................................................................................55.Reflection..................................................................................................................................55.1Howwelldidtheapproacheswork.............................................................................................56.Appendix...................................................................................................................................66.1Definitions...................................................................................................................................6
PlansProposalforOSEKOSDevelopmentPageiii
RevisionHistory
DocumentVersionDateChangesAuthorManager
Yoon-Phil0.110/14/06CreatedinitialdraftTaehoKimKim
Yoon-Phil0.210/15/06ComplementtheinitialdraftTaehoKimKim
PlansProposalforOSEKOSDevelopmentPage1
1.Introduction
InProposalDrivenStudio,softwarestudioprojectsarebrokendownintotechnological,people,and
processconcerns.Ratherthandefinespecificapproachesthatthestudentsmustuseandartifactsthat
mustbeproducedaswecurrentlydo,intheproposalbasedstudio,studiofacultyandmentorsask
studentstocreateproposalsforeachdimensionastheyappearabove.ThePlansproposalwillbea
livingdocumentthatwillcontainseveralsections:
context,approaches,analysis,andreflection.
Initially,theproposalwillprovidecontext,defineapproaches,andastrategyforanalysis.Afterthe
approachandanalysissection,theteamwilladdthefinalsectionthatdiscussestheirreflectionupon
theapproachesandanalysistechniquesandmethodsthattheyselected.
Concern:
People&Process–Dimension:
PlansDefinitionReferstotheplanning,scheduling,managing,tracking,and
oversightoftheprojectandteam.ApproachesSelectmethods,techniques,andstrategiesforplanning,
managing,andcontrollingtheactivitiesoftheproject.(Examples
include:
ETVX,PertCharts,GanttCharts,CriticalChain)
AnalysisVerifythattheteamisadheringtoscheduleandresource
commitments.(Examplesinclude:
Datacollection,EarnedValue,
StatisticalAnalysis.)
ReflectionHowwelldidthesemethodswork?
Facedwithasimilarsituation,
whatwouldyoudonexttime?
Reference
[1]ProposalDrivenStudioV2.02005—AnthonyJ.Lattanze—AdaptedbyGraceLewis
PlansProposalforOSEKOSDevelopmentPage2
2.Context
2.1Projectoverview
Willbedefinedinchapter2.1ofSOW
2.2Teamname
Infinite
WewilltrytodevelopanInfiniteOperatingSystemwithourInfinitepotential.
2.3Teammembers
EunjeongChoi
JihyunLee
TaehoKim
Yoon-PhilKim
2.4ProjectDimensionofThisProposal
Theprojectdimensionofthisproposalisplanning.Theplanproposalincludesapproaches,analysis
andreflectionsofplanning.
•Approach–includesmethods,techniques,andstrategiesthatcouldbeusedbyInfiniteteam
throughtheproject.•Analysis–includesmethods,techniques,andstrategiesthatTrinitywillusetoanalyzethe
effectivenessoftheapproachesTrinityselected.•Reflection–isa―hindsightanalysis‖ofusingaparticularsetoftechniques
PlansProposalforOSEKOSDevelopmentPage3
3.Approaches
3.1Methods
ThemethodstoplanthestudioprojectfortheInfiniteteamwillbetheSoftwareProjectManagementPlan(SPMP).TheSPMPwillguidetheoveralloperationoftheprojectandwillincludealloftheplanningtasksforthestudioproject.OurSPMPwillbedescribedbasedontheIEEEStd1058-1998-IEEEStandardforSoftwareProjectManagementPlans.
TheSPMPwillincludeconfigurationmanagementplan,qualityassuranceplan,riskmanagementplanandverificationandvalidationplan.However,ifthepagesizeofeachsub-plandocumentsis
growing,itcouldbeseparatedfromSPMP.
3.2Techniques
ThisdetailedschedulewillbedescribedasaGanttchartcreatedbyMicrosoftProject.SinceGanttchartsareeasytoconstruct,theyprovideseveralbenefits:
theyallowtheteammemberstovisuallydeterminetheorderofthetasksandtheassignmentofthetaskstoindividuals;theyallowtheplanmanagertosimplydeterminewhethertheprojectisonscheduleornot.
Theteam’stechniquetocontroltheprojectwillbeProgramEvaluationandReviewTechnique
(PERT)Charts.PERTchartsprovideusefulinformationsuchasthestartandenddatesofallofthetasks,whichtasksaredelaying,andwhichtasksareonthecriticalpath.Theteamwillperiodicallymonitorthetasksonthecriticalpathtofindoutwhichtaskswillbeaffectedtoprogresstheproject.Theteamwillcontroltheprojectbyallocatingresourcesfromtaskswithdelayingtimetotasksonthecriticalpathifnecessary.PERTanalysiscouldbeperformedbyMicrosoftProjectfunctions.
3.3Strategies
TheSPMPwillnotincludethedetailedprojectschedule,sothedetailedprojectschedulewillbeaddressedonthestudioprojectscheduledocument.Atthefirstsemester,thescheduleforthefirstsemestershouldbedescribedindetailbutscheduleforothersemesterswouldbebrieflyoutlined.
Duringthestudioproject,theindividualteammembersshoulddeveloptheirownskillsfordifferentjobs.Tolearntheskills,theteammemberswillrotatetherolesandassignnewrolestoindividualsatthebeginningofeachsemester.Amongtheroles,theteamleadisresponsibleforleadingtheteamandalsoholdstheroleoftheplanmanager.Therefore,therewillbeanewplanmanageroneachsemester.Atthebeginningofeachsemester,theplanmanagerwillcreateadetailedscheduleforthesemesterincludingweeklytasksforeachoftheteammembers.Atthattime,theinitialprojectscheduleforallsemestersshouldbere-estimated,andthetasksarere-initiatedaccordingtotheschedule.
Duringweeklystatusmeeting,theprojectteamwillbetrackingtasksandrisks.
TrackingtaskswillbeaccomplishedusingMicrosoftProjectbysimplycomparingthetaskscompletedtothetaskssupposedtohavebeencompleted.Thepurposeoftrackingtasksistocheckwhethertheplannedtasksarecompletedontimeornot.
PlansProposalforOSEKOSDevelopmentPage4
Trackingriskshelpstoadvancetheprogressoftheproject.Riskscanbeissuedduringtheprojectandeachriskhasthepotentialtomaketheprojectdelay.Trackingriskswillbeperformedthrougharisktracker.
Weeklystatusreportswillprovideregularcommunicationamongtheteam,thementors,andthecustomer.Theweeklystatusreportwilladdressanyoutstandingrisks,unresolveddefects,ormissedactivities.
3.4Artifacts
SoftwareProjectManagementPlan(MicrosoftWord)
StudioProjectSchedule(MicrosoftProject)
RisksTracker(MicrosoftExcel)
3.5References
[2]IEEEStandardforSoftwareProjectManagementPlans(IEEEStd
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IEEESoftwareRequirementsSpecificationTemplate
![提示](https://static.bdocx.com/images/bang_tan.gif)
链接地址:https://www.bdocx.com/doc/24603918.html