ACS 560 – SOFTWARE ENGINEERING Course Accomplishment Summary Shilpashree K.S Fall 2010 Purdue University – Fort Wayne Instructor – Dr. John Tanik.

Slides:



Advertisements
Similar presentations
COMET Approach for UML Overview
Advertisements

Ch 3 System Development Environment
Object-Oriented Analysis and Design
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Object-Oriented Analysis and Design
Rational Unified Process
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
SE 470 Software Development Processes James Nowotarski 21 April 2003.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
© Copyright Eliyahu Brutman Programming Techniques Course.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 1.
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
Requirements Engineering
Guide to the Software Engineering Body of Knowledge Chapter 1 - Introduction.
CS 4310: Software Engineering Lecture 3 Requirements and Design.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
RUP Fundamentals - Instructor Notes
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
ACS 562 – SYSTEMS ANALYSIS AND DESIGN Course Accomplishment Summary Shilpashree K.S Varsha Fall 2010 Purdue University – Fort Wayne Instructor – Dr. John.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Chapter 1: Introduction to Systems Analysis and Design
Software Requirements Engineering CSE 305 Lecture-2.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Chapter – 9 Checkpoints of the process
Chapter 7 Applying UML and Patterns Craig Larman
Chapter 7 System models.
Lecture 7: Requirements Engineering
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
Rational Unified Process Fundamentals Module 3: Disciplines I.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Introduction to OOAD and the UML
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
1. The Requirements Process Requirements Input Example
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
© 2000 Franz Kurfess System Design Methods 1 CSC 205: Software Engineering I Dr. Franz J. Kurfess Computer Science Department Cal Poly.
Monica Gloudemans Ekaterina Schwartz Gloudemans/Schwartz ACS 560 CMAP.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Requirement Engineering Management Amna Shifia Nisafani Feby Artwodini M. Department of Information Systems Subject : Requirement Engineering.
CompSci 280 S Introduction to Software Development
Software Design Lecture : 15.
OO Design and Development
Requirements Document
System architecture, Def.
Introduction to OOAD and the UML
UML Design for an Automated Registration System
Presentation transcript:

ACS 560 – SOFTWARE ENGINEERING Course Accomplishment Summary Shilpashree K.S Fall 2010 Purdue University – Fort Wayne Instructor – Dr. John Tanik

PART 1 Study on C-Map Study on C-Map Research on project topic Research on project topic Study and Review (Summary) of Text Book Chapters Study and Review (Summary) of Text Book Chapters Review of the Scholarly papers Review of the Scholarly papers Summarize SWEBOK Knowledge Areas Summarize SWEBOK Knowledge Areas

Project Topic Research Went Through 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 Reviews Part I: UML Notation, Design Concepts, Technology, Life Cycles and Methods Chapter 1 : Introduction Chapter 1 : Introduction Chapter 2: Overview of UML Notation Chapter 2: Overview of UML Notation Chapter 3: Software Design and Architecture Concepts Chapter 3: Software Design and Architecture Concepts Chapter 4: Concurrent and Distributed System Technology Chapter 4: Concurrent and Distributed System Technology Chapter 5: Software Life Cycles and Methods Chapter 5: Software Life Cycles and Methods

Chapter Reviews Part II: COMET: Concurrent Object Modeling And Architectural Design With UML Chapter 6 : Overview of COMET Chapter 6 : Overview of COMET Chapter 7 : Use Case Modeling Chapter 7 : Use Case Modeling Chapter 8 : Static Modeling Chapter 8 : Static Modeling Chapter 9 : Object and Class Structuring Chapter 9 : Object and Class Structuring Chapter 10 : Finite State Machines And Statecharts Chapter 10 : Finite State Machines And Statecharts Chapter 11 : Dynamic Modeling Chapter 11 : Dynamic Modeling Chapter 12 : Software Architecture Design Chapter 12 : Software Architecture Design Chapter 13 : Architectural Design of Distributed Applications Chapter 13 : Architectural Design of Distributed Applications Chapter 14 : Task Structuring Chapter 14 : Task Structuring Chapter 15 : Class Design Chapter 15 : Class Design Chapter 16 : Detailed Software Design Chapter 16 : Detailed Software Design

Review 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 Areas KA 1: Software Requirements KA 1: Software Requirements KA 2: Software Design KA 2: Software Design KA 3: Software Construction KA 3: Software Construction KA 4: Software Testing KA 4: Software Testing KA 5: Software Maintenance KA 5: Software Maintenance KA 6: Software Configuration Management KA 6: Software Configuration Management KA 7: Software Engineering Management KA 7: Software Engineering Management KA 8: Software Engineering Process KA 8: Software Engineering Process KA 9: Software Engineering Tools and Methods KA 9: Software Engineering Tools and Methods KA 10: Software Quality KA 10: Software Quality KA 11: Knowledge Areas of Related Desciplines KA 11: Knowledge Areas of Related Desciplines

PART 2 Implementation of Inception Phase of RUP Implementation of Inception Phase of RUP Implementation of Elaboration Phase of RUP Implementation of Elaboration Phase of RUP

Implementation of Inception Phase

Research Research Business Modeling Business Modeling Requirements Requirements Analysis and Design Analysis 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 – Chronic Disease Alliance: A Unified Approach Chronic Disease Alliance: A Unified Approach

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 Modeling A general vision of the core project’s requirements, key features, and main constraints Vision Document: A general vision of the core project’s requirements, key features, and main constraints which includes business context, success criteria, and financial forecast An Initial Business Case Document which includes business context, success criteria, and financial forecast

Requirements Voice of Customer Document Customer Needs Document Functional Requirements Document Project Glossary Document

Analysis and Design Axiomatic Design Initial Use Case Model Project Plan Initial Risk Assessment

Axiomatic Design FR-DP Design Matrix

Axiomatic Design DP-DP Design Matrix

Axiomatic Design Customer Needs

Axiomatic Design FR-DP Decomposition

Axiomatic Design Quality Function Deployment

An Initial Use Case Model

Project Plan

Project Plan (Contd)

Risk Analysis

Implementation of Elaboration Phase

Business Modeling Requirements Analysis and Design

Business Modeling which includes business context, success criteria, and financial forecast Business Case Document which includes business context, success criteria, and financial forecast

Software Requirements Specification Introduction Introduction Overall Description Overall Description – Product Perspective, Product Functions, User Characteristics, Stakeholder Needs, General Constraint, Assumptions & Dependencies Specific Requirements Specific Requirements – Functional Requirements – External Interface Requirements – Performance Requirements – Design Constraints – Software System Attributes – Other Requirements

Software Requirements Specification

Software 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 Diagram

UML Modeling Data Flow Diagram

UML Modeling Activity Diagram

UML Modeling Sequence Diagram

UML Modeling Class Diagram

UML Modeling State Chart Diagram

UML Modeling Deployment Diagram

SysML Modeling Requirements Diagram

SysML Modeling Activity Diagram

Thank You