SW-PHASE 3 Simple explanation for what we will submit.

Slides:



Advertisements
Similar presentations
Chapter 10 Architectural Design.
Advertisements

Chapter 7 System Models.
IS301 – Software Engineering Dept of Computer Information Systems
Week 2 The Object-Oriented Approach to Requirements
Object-Oriented Software Engineering Visual OO Analysis and Design
Lecture 6: Software Design (Part I)
Chapter 10: The Traditional Approach to Design
Systems Analysis and Design in a Changing World, Fifth Edition
Modeling Main issues: What do we want to build How do we write this down.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Communication Notation Part V Chapter 15, 16, 18 and 19.
Software Architecture Design Instructor: Dr. Jerry Gao.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
SWE Introduction to Software Engineering
Establishing the overall structure of a software system
Course Instructor: Aisha Azeem
Chapter 6: Architectural Design
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 3 Relational Model Chapter 4 in Textbook.
Chapter 6 The Traditional Approach to Requirements
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Systems Analysis and Design in a Changing World, Fifth Edition
Systems Analysis And Design © Systems Analysis And Design © V. Rajaraman MODULE 14 CASE TOOLS Learning Units 14.1 CASE tools and their importance 14.2.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
CS451 Lecture 13: Architectural Design Chapter 10
Architectural Design. Recap Introduction to design Design models Characteristics of good design Design Concepts.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 13Slide 1 Architectural Design u Establishing the overall structure of a software system.
Architectural Design portions ©Ian Sommerville 1995 Establishing the overall structure of a software system.
Architectural Design To explain the advantages and disadvantages of different distributed systems architectures To discuss client-server and distributed.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Methodologies of the SDLC Traditional Approach to SDLC Object-Oriented Approach to SDLC CASE Tools.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Architectural Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Chapter 8 Methodology - Conceptual Database Design Chapter 15 in Textbook.
 Repository Model  Client-Server Model  Layered Model  Modular decomposition styles  Object Models  Function Oriented Pipelining  Control Styles.
CS 3630 Database Design and Implementation. Assignment 1 2 What is 3630?
Dr.Basem Alkazemi
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
1 CMPT 275 High Level Design Phase Modularization.
Chapter 7: Architectural Design Chapter 11 in textbook 1.
CSC480 Software Engineering Lecture 10 September 25, 2002.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Modelling Methodologies Chapter 16, 17, 18. Modeling Methodologies2 Database Design Physical DB design Logical DB design Conceptual DB design Hardware.
Lecture VIII: Software Architecture
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Slide 1 Chapter 8 Architectural Design. Slide 2 Topics covered l System structuring l Control models l Modular decomposition l Domain-specific architectures.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.
CompSci 280 S Introduction to Software Development
CS 3630 Database Design and Implementation
Part 3 Design What does design mean in different fields?
Project 1 Guide System Analysis & Design
Conceptual Database Design
CS 425/625 Software Engineering Architectural Design
Princess Nourah bint Abdulrahman University
IT323 Project Phase#2.
Presentation transcript:

SW-PHASE 3 Simple explanation for what we will submit

SW design In this phase we will design the software of E-student notebook Software design phase contains: Architectural design Data Design Component Design Interface Design

Architectural design The design process of identifying the sub- systems making up a system and establishing a framework for sub-system control and communication. An early stage of the system design process. Represents the link between specification (requirements engineering process) and design processes.

1- Architectural design It involves identifying major system components and their communications. The software architect must make decisions about: System organization style Strategy for decomposing sub-systems into their components or modules How the execution of sub-systems is controlled

1.1 System organization style Client-server organization style Shared data repository style Layered architecture style Different parts of the system may be designed using different architectural styles.

1.2 Strategy for decomposing sub- systems into their components or modules – An object-oriented decomposition model where the system is decomposed into interacting objects – A Function-oriented pipelining (or data-flow model) where the system is decomposed into functional modules that accept input data and transform it into output data.

1.3 How the execution of sub-systems is controlled Centralised control One sub-system has overall responsibility for control and starts and stops other sub- systems. Event-based control Each sub-system can respond to externally generated events from other sub-systems or the system’s environment.

2- Data Design ER Database Schema Data Dictionary

Lilac Safadi Conceptual DB Design 2.1 EXAMPLE: ERD for Staff View of DreamHome BUSINESS OWNER STAFF PROPERTY PRIVATE OWNER LEASE CLIENT PREFERENCE POwn holdassociate manage state superviseregister BOwn (1:1) (0,*) (0,1) (1,*) (0,1) (0,100) views (0,*) supervisor supervisee

Lilac Safadi Relational Model Relation Schema StudentNo Al-Saleh Al-Ghanem Al-Fahad Saod Rashed LName Amal Nora Laila Amal Rana FNameInitial M. A. F. I. DOB GPA STUDENT Dept D001 D002 D003 D001 STUDENT (StudentNo, Lname, Fname, Initial, DOB, GPA, Dept) We will do same as this for all relations we have =)

Lilac Safadi Conceptual DB Design 2.3 Data Dictionary for Staff View Showing Description of Relationships Entity Name Multiplicity Relationship Entity Name Multiplicity Staff 0..1 Manages PropertyForRent Supervises Staff PropertyForRent 1..1 AssociatedWith Lease 0..*

3- Component Design If you use Structured System analysis: DFD. Pseudo-code.

3- Component Design If you Use Object-Oriented: - Use case diagram. - Class diagram. - Pseudo-code.

3- Component Design If you Use Object-Oriented: I think Using OOP is much easier for us than DFDs specially with the help of eclipse using UML and Code Review :Enerjy the 1 st will generate most of the code and the 2ed will validate it. With DFDs the probability of making mistake is huge this is what I think, TELL ME WUT U THINK ^^

Use case diagram

Class diagram

EDRAW TOOLS If you did not download eclipse or you don’t know how to create UML or DFDs These are online tools to help you draw and do your part =) gn.asp gn.asp Diagrams.php Diagrams.php

Pseudo-code Example = if do stuff else do other stuff while do stuff for from to by do stuff with variable function ( ) do stuff with arguments return something ( ) // Function call

4- Interface Design In this section, we want to see what the system is going to look like to the person who will be operating/using it. (Print screen for the main functions, error messages, etc…). We could use Visual Basic.Net Or Web design Check the One Note for Microsoft office interface we should do something like it

Work Breakdown

NamePart 1Part 2Part 3Part 4 Reem** Rathath** Rawan** Hessah** Fatima** Hayfa** Farah** Reham** Phase partsDuration 1- Archi Design 2 days 2-Data Design2 days 3-Component Design 2 days 4-Interface1 day Total duration : 7 daysDue date : Sat 2 – 5 – 2009 (*) Means : u r participating in the part

For part 1 ( Reem, Hayfa, Rawan, Farah, Hessah) We should go out tomorrow morning in algara3awi at 9 am till I dunno we get tired Bring ur laptops and charge them If u can’t come let me know by a msg But plz we NEED to get it done together So try hard to come next morning Thank you,