R R R CSE870: Advanced Software Engineering: Cheng (Sp 2001)CSE870: Advanced Software Engineering: Cheng (Sp 2001)1 Mini Project An Overview.

Slides:



Advertisements
Similar presentations
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
10 Software Engineering Foundations of Computer Science ã Cengage Learning.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
The Rhapsody in C++ Tool Training "Essential" © I-Logix v2.3 25/9/2000 EI-1 “Essential” Rhapsody in C++ Introduction.
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
The Architecture Design Process
0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
Chapter 1 Software Engineering. Homework ► Read Section 2.2 (pages 79-98) ► Answer questions: ► 7, 8, 11, 12, & 13 on page 134. ► Answer on paper, hand.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
0-1 Team ?? Status Report (1 of 3) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team 1: Auraria.
Session 7 Page 11 ECE361 Engineering Practice Brainstorming, Trades, Evaluation, and Conceptual Capture.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Architecture, Implementation, and Testing Architecture and Implementation Prescriptive architecture vs. descriptive architecture Prescriptive architecture:
CIS 321—IS Analysis & Design
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
1 Shawlands Academy Higher Computing Software Development Unit.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Mapping Designs to Code Larman, Chapter 20 CSE432 Object Oriented Software Engineering.
Adaptive Processes © Adaptive Processes Simpler, Faster, Better Software Requirements.
4/2/03I-1 © 2001 T. Horton CS 494 Object-Oriented Analysis & Design Software Architecture and Design Readings: Ambler, Chap. 7 (Sections to start.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
Information System Development Courses Figure: ISD Course Structure.
Methods and Models Choice of methods for Development of IT related products and systems SVINGSVING Conference held in Gothenburg, Sweden, October 2000.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
CASE Tools Union Palenshus. In the early days… ► Software engineering tools consisted solely of translators, compilers, assemblers, linkers, loaders,
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
POS406 Team Project Emilio Yanine. Team Assignment Your assignment is to analyze and understand the code of a sample program: 1. Be able to identify the.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
The Software Development Process
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
Reflecting Proxies Mini != Small Jon Babbage Tony Lambert Michael Malinak Paul Middlin CSE870 Advanced Software Engineering, Spring 2001 Instructor: Dr.
Final Class Diagram for C++ Implementation Clickermatic Software Clicker.
Lab 5 CPIT 250 System Analysis and Design.
CONTENT 1.Software Process 2.Object Technology 3.UML 4.UML For Java.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
1 OO Analysis & Design - Introduction to main ideas in OO Analysis & design - Practical experience in applying ideas -A large element is use of UML as.
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Object Oriented Analysis and Design 1 Chapter 9 From Design to Implementation  Implementation Model  Forward, Reverse, and Round-Trip Engineering  Mapping.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
4+1 View Model of Software Architecture
Object-Oriented Software Engineering Practical Software Development using UML and Java Modelling with Classes.
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
Fall 2007 Week 11: Object Modeling (2) Class Diagram MSIS 670: Object-Oriented Software Engineering.
Object Oriented Analysis & Design By Rashid Mahmood.
OBJECT ORIENTED VS STRUCTURED WHICH ONE IS YOUR CHOICE.
1 Framework Presentation Project Participants: Karun Biyani Manish Mehta Pradeep Vincent CSE870 Advanced Software Engineering, Spring 2001 Instructor:
Advanced Software Engineering Dr. Cheng
CSE784 – Software Studio Jim Fawcett Fall 2002.
CMPE 280 Web UI Design and Development August 29 Class Meeting
Unified Modeling Language
CSE784 – Software Studio Jim Fawcett Fall 2006.
Software Design Methodology
Framework Presentation
Team members: Project Manager: Facilitator: Customer Liason:
Systems Analysis Overview.
EECE 310 Software Engineering
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Object Oriented Analysis and Design
Team Members: Member1, … Spring 2013
Presentation transcript:

R R R CSE870: Advanced Software Engineering: Cheng (Sp 2001)CSE870: Advanced Software Engineering: Cheng (Sp 2001)1 Mini Project An Overview

R R R CSE870: Advanced Software Engineering: Cheng (Sp 2001)CSE870: Advanced Software Engineering: Cheng (Sp 2001)2 Build a Framework Your assignment is to create a framework, following these steps. 1.Work in teams of 3. 2.Identify three existing applications (call them App1, App2, App3) all within the same application domain. –Each should involve a small number of classes –that are tightly integrated. 3.Start with App1 and create a whitebox framework. –Refactor as necessary to make the framework more general. –Use UML class diagrams to depict the framework hierarchy.

R R R CSE870: Advanced Software Engineering: Cheng (Sp 2001)CSE870: Advanced Software Engineering: Cheng (Sp 2001)3 Assignment Cont’d 4.Instantiate the framework to generate the first existing application, App1. 5.Attempt to apply the framework to your second existing application, App2. –Generalize the framework so that it will fit the constraints imposed by App2. 6.Instantiate the framework to generate the first two existing applications, App1 and App2. 7.Repeat Step 5 and 6 to App3 to yield a third iteration of the Framework and implementation of App3 using the third iteration of the Framework.

R R R CSE870: Advanced Software Engineering: Cheng (Sp 2001)CSE870: Advanced Software Engineering: Cheng (Sp 2001)4 Evaluation 1.You must NOT use an existing framework. –Doing so will result in a 0 for the miniproject. 2.The level of detailed documentation for each of the above steps in the framework development process. –There must be complete traceability from initial work with App1 to the final iteration with building all three applications. –UML diagrams need to be included and described in the description of the frameworks. 3.If you achieve gray box framework status for your final framework, –you will be eligible for 85% evaluation for the miniproject –(assuming that all other aspects of the project are satisfactory). 4.If you achieve black box framework status for your final framework, –you will be eligible for 100% evaluation for the miniproject –(assuming that all other aspects of the project are satisfactory). 5.All 3 frameworks must be documented and turned in with the final project report. –It must be clearly described as to from one iteration of the framework to the next.

R R R CSE870: Advanced Software Engineering: Cheng (Sp 2001)CSE870: Advanced Software Engineering: Cheng (Sp 2001)5 Project Domain Any type of proxies They tend to be smaller applications, involving a few classes –Filtering –Security –Caching –Anonymous: –Compression/decompression Definition: Proxies are pieces of software that reside between the client and server to perform some intermediate action.

R R R CSE870: Advanced Software Engineering: Cheng (Sp 2001)CSE870: Advanced Software Engineering: Cheng (Sp 2001)6 Project Constraints Language: C++ or Java Applications must involve a collection of highly interactive classes –Must have at least 2-3 classes to define framework. Must have legal access to source code Must be able to demonstrate functionality of proxies BEFORE and AFTER framework construction When in doubt, ask questions