ACS 560 – SOFTWARE ENGINEERING Course Accomplishment Summary Shilpashree K.S Fall 2010 Purdue...
-
Upload
warren-hopkins -
Category
Documents
-
view
214 -
download
0
Transcript of ACS 560 – SOFTWARE ENGINEERING Course Accomplishment Summary Shilpashree K.S Fall 2010 Purdue...
ACS 560 – SOFTWARE ENGINEERINGACS 560 – SOFTWARE ENGINEERINGCourse Accomplishment Summary Course Accomplishment Summary
Shilpashree K.S
Fall 2010
Purdue University – Fort Wayne
Instructor – Dr. John Tanik
PART 1PART 1
• Study on C-MapStudy on C-Map
• Research on project topicResearch on project topic
• Study and Review (Summary) of Text Study and Review (Summary) of Text Book ChaptersBook Chapters
• Review of the Scholarly papersReview of the Scholarly papers
• Summarize SWEBOK Knowledge Summarize SWEBOK Knowledge AreasAreas
Project Topic ResearchProject Topic Research
• Went Through http://www.openclinical.org/
http://www.purdue.edu/discoverypark/rche/ to get more details about biomedical research field
• Surveyed the nutrition requirement and exercises for various types of people depending on their life style from various websites
• Created a draft version of the Project proposal for “Health Monitor – Managing Diet and Fitness for Healthy Living”
Chapter ReviewsChapter Reviews
Part I: UML Notation, Design Concepts, Technology, Part I: UML Notation, Design Concepts, Technology, Life Cycles and MethodsLife Cycles and Methods
• Chapter 1 : IntroductionChapter 1 : Introduction
• Chapter 2: Overview of UML NotationChapter 2: Overview of UML Notation
• Chapter 3: Software Design and Architecture ConceptsChapter 3: Software Design and Architecture Concepts
• Chapter 4: Concurrent and Distributed System Chapter 4: Concurrent and Distributed System TechnologyTechnology
• Chapter 5: Software Life Cycles and MethodsChapter 5: Software Life Cycles and Methods
Chapter ReviewsChapter Reviews
Part II: COMET: Concurrent Object Modeling And Part II: COMET: Concurrent Object Modeling And Architectural Design With UMLArchitectural Design With UML
• Chapter 6 : Overview of COMETChapter 6 : Overview of COMET• Chapter 7 : Use Case ModelingChapter 7 : Use Case Modeling• Chapter 8 : Static ModelingChapter 8 : Static Modeling• Chapter 9 : Object and Class StructuringChapter 9 : Object and Class Structuring• Chapter 10 : Finite State Machines And StatechartsChapter 10 : Finite State Machines And Statecharts• Chapter 11 : Dynamic ModelingChapter 11 : Dynamic Modeling• Chapter 12 : Software Architecture DesignChapter 12 : Software Architecture Design• Chapter 13 : Architectural Design of Distributed Chapter 13 : Architectural Design of Distributed
ApplicationsApplications• Chapter 14 : Task StructuringChapter 14 : Task Structuring• Chapter 15 : Class DesignChapter 15 : Class Design• Chapter 16 : Detailed Software DesignChapter 16 : Detailed Software Design
Review of the Scholarly PapersReview of the Scholarly Papers
• Representing Clinical Guidelines in UML: A Comparative Study
• A UML Approach to Process Modelling of Clinical Practice Guidelines for Enactment
• Enhancing Object-Oriented Software Development through Axiomatic Design.
• A UML 2.0 Profile for SystemC: Toward Highlevel SoC Design
• SysML and Systems Engineering Applied to UML based SoC Design
• Designing Real-Time and Embedded Systems with the COMET / UML method
Summarize SWEBOK Knowledge Summarize SWEBOK Knowledge AreasAreas
• KA 1: Software RequirementsKA 1: Software Requirements• KA 2: Software DesignKA 2: Software Design• KA 3: Software ConstructionKA 3: Software Construction• KA 4: Software TestingKA 4: Software Testing• KA 5: Software MaintenanceKA 5: Software Maintenance• KA 6: Software Configuration ManagementKA 6: Software Configuration Management• KA 7: Software Engineering ManagementKA 7: Software Engineering Management• KA 8: Software Engineering ProcessKA 8: Software Engineering Process• KA 9: Software Engineering Tools and MethodsKA 9: Software Engineering Tools and Methods• KA 10: Software QualityKA 10: Software Quality• KA 11: Knowledge Areas of Related DesciplinesKA 11: Knowledge Areas of Related Desciplines
PART 2PART 2
• Implementation of Inception Phase of Implementation of Inception Phase of RUPRUP
• Implementation of Elaboration Phase Implementation of Elaboration Phase of RUPof RUP
Implementation of Inception PhaseImplementation of Inception Phase
Implementation of Inception Implementation of Inception PhasePhase
•ResearchResearch
•Business ModelingBusiness Modeling
•RequirementsRequirements
•Analysis and DesignAnalysis and Design
Research Research
•DIET, NUTRITION AND THE PREVENTION OF CHRONIC DISEASES
•Diet and Nutrition Surveillance for Chronic Disease: A White Paper on the National Report on Biochemical Indicators of Diet and Nutrition in the U.S. Population – 1999-2002
•Chronic Disease Alliance: A Unified Chronic Disease Alliance: A Unified ApproachApproach
Research Research
•Preventing Chronic Disease : Public Health Research, Practice, and Policy
•Low-Fat Diet and Chronic Disease Prevention: the Women’s Health Initiative and Its Reception
•Pennsylvania Nutrition and Physical Activity Plan to Prevent Obesity and Related Chronic Diseases: Department of Health
Research Research
• OMG Systems Modeling Language Tutorial
• Introduction to UML
• IEEE recommended practice for software requirements specifications.
• IEEE 1016 – Recommended Practices for Software Design Description
Business ModelingBusiness Modeling
• Vision Document: A general vision A general vision of the core project’s requirements, of the core project’s requirements, key features, and main constraintskey features, and main constraints
• An Initial Business Case Document which includes business context, which includes business context, success criteria, and financial success criteria, and financial forecastforecast
RequirementsRequirements
• Voice of Customer Document
• Customer Needs Document
• Functional Requirements Document
• Project Glossary Document
Analysis and DesignAnalysis and Design
• Axiomatic Design
• Initial Use Case Model
• Project Plan
• Initial Risk Assessment
Axiomatic DesignAxiomatic DesignFR-DP Design MatrixFR-DP Design Matrix
Axiomatic DesignAxiomatic DesignDP-DP Design MatrixDP-DP Design Matrix
Axiomatic DesignAxiomatic DesignCustomer NeedsCustomer Needs
Axiomatic DesignAxiomatic DesignFR-DP DecompositionFR-DP Decomposition
Axiomatic DesignAxiomatic DesignQuality Function DeploymentQuality Function Deployment
An Initial Use Case ModelAn Initial Use Case Model
Project PlanProject Plan
Project Plan (Contd)Project Plan (Contd)
Project Plan (Contd)Project Plan (Contd)
Risk AnalysisRisk Analysis
Implementation of Elaboration PhaseImplementation of Elaboration Phase
Implementation of Elaboration PhaseImplementation of Elaboration Phase
• Business Modeling
• Requirements
• Analysis and Design
Business ModelingBusiness Modeling
• Business Case Document which which includes business context, success includes business context, success criteria, and financial forecastcriteria, and financial forecast
Software Requirements SpecificationSoftware Requirements Specification
• IntroductionIntroduction
• Overall DescriptionOverall Description
– – Product Perspective, Product Functions, User Product Perspective, Product Functions, User Characteristics, Stakeholder Needs, General Constraint, Characteristics, Stakeholder Needs, General Constraint, Assumptions & DependenciesAssumptions & Dependencies
• Specific RequirementsSpecific Requirements
– – Functional RequirementsFunctional Requirements
– – External Interface RequirementsExternal Interface Requirements
– – Performance RequirementsPerformance Requirements
– – Design ConstraintsDesign Constraints
– – Software System Attributes Software System Attributes
– – Other RequirementsOther Requirements
Software Requirements SpecificationSoftware Requirements Specification
Software Requirements SpecificationSoftware Requirements Specification
Software Design DescriptionsSoftware Design Descriptions
• Overview– Introduction, Purpose, Scope, Assumptions
and General Constraints, Definitions, Reference Documents• Stakeholder
– Identification, Concerns• Software Architecture Overview
– Viewpoint - Views Summary, Architecture Goals and
Constraints• Architecture Viewpoint
– Architecture Viewpoint summary, UML & SysML
diagram
System Block DiagramSystem Block Diagram
UML ModelingUML ModelingData Flow DiagramData Flow Diagram
UML ModelingUML ModelingActivity DiagramActivity Diagram
UML ModelingUML ModelingActivity DiagramActivity Diagram
UML ModelingUML ModelingSequence DiagramSequence Diagram
UML ModelingUML ModelingClass DiagramClass Diagram
UML ModelingUML ModelingState Chart DiagramState Chart Diagram
UML ModelingUML ModelingDeployment DiagramDeployment Diagram
SysML ModelingSysML ModelingRequirements DiagramRequirements Diagram
SysML ModelingSysML ModelingActivity DiagramActivity Diagram
Thank YouThank You