1 Week 6 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

TOPIC : SYNTHESIS DESIGN FLOW Module 4.3 Verilog Synthesis.
Karolina Muszyńska Based on:
Modeling Main issues: What do we want to build How do we write this down ©2008 John Wiley & Sons Ltd. vliet.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Human Computer Interaction
2008/03/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Introduction To System Analysis and Design
Systems Analysis and Design in a Changing World, Fourth Edition
© Copyright Eliyahu Brutman Programming Techniques Course.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
SE-565 Software System Requirements More UML Diagrams.
Chapter 13: Designing the User Interface
Chapter 7: The Object-Oriented Approach to Requirements
Introduction To System Analysis and design
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
The Software Development Life Cycle: An Overview
CIS 321—IS Analysis & Design
Managing the development and purchase of information systems (Part 1)
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
COE4OI5 Engineering Design. Copyright S. Shirani 2 Course Outline Design process, design of digital hardware Programmable logic technology Altera’s UP2.
UML & Prototyping. What is a prototype? A prototype is a small-scale model. It can be (among other things): a series of screen sketches a storyboard,
Chapter 8: Actor-System Interaction Modeling
Automating Database Processing Chapter 6. Chapter Introduction Design and implement user-friendly menu – Called navigation form Macros – Automate repetitive.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
HCI – Prototyping. Why Prototype?  Prototyping is a well understood and used technique in design engineering where products are tested via a model prototype.
Introduction To System Analysis and Design
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 Moving to Design
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
1 Introduction to Software Engineering Lecture 1.
To navigate the slide presentation, use the navigation bar on the left OR use your right and left arrow keys. Move your mouse over the key terms throughout.
Sept. 18, 2003CS WPI1 CS 509 Design of Software Systems Lecture #3 Thursday, Sept. 18, 2003.
Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Courselist Project Automated Graduate Student Information System Final project for CS 3354.
CIS 112 Exam Review. Exam Content 100 questions valued at 1 point each 100 questions valued at 1 point each 100 points total 100 points total 10 each.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Essentials of OVID Using UML based notation to capture system requirements and design.
Systems Analysis and Design in a Changing World, Fourth Edition
UML Activity Diagrams.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 Using Rational Rose ® to construct UML diagrams.
CS 5150 Software Engineering Lecture 9 Requirements 3.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
Live. learn. work. play Superior Avenue Suite 310 Cleveland Ohio Tel: Fax:
1 An Overview of UML. 2 The Unified Modeling Language UML is a graphical language used by software engineers to model software systems during development.
1 Week 5 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
1 Week 7 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
Software Engineering 2007/2008 Chapter 5 Designing the System.
School of Business Administration
School of Business Administration
Object-Oriented Analysis and Design
Week 10: Object Modeling (1)Use Case Model
Software Architecture & Design Pattern
UML Activity Diagrams.
Introduction To System Analysis and Design PART 2
Chapter 20 Object-Oriented Analysis and Design
Usability Techniques Lecture 13.
Appendix A Object-Oriented Analysis and Design
Analysis models and design models
CS 8532: Advanced Software Engineering
UML Design for an Automated Registration System
Chapter 8: Actor-System Interaction Modeling
Presentation transcript:

1 Week 6 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam

2 Quiz 2 Review Mini-Project 2 Planning Chapter 7 Design: Architecture & Methodology

3 Essentials of Software Engineering Chapters 4-6 UML Distilled Chapter 9

4

5

6

7

8

9

10

11

12

13 Suggestion: Use Quicktime video player VTC Preparation for Week 6

14 CS3/MP3 Preparation

15 SoftwareSoftware

16 Search: Gane-Sarson Frame Title Blocks

17 Crow’s Foot Database Notation

18

19 1. Explain the role of requirements in architectural design. Explain the role of requirements in detail design. Ans: The role of requirements in architectural design can be described as: a transformational step where the requirements are the input and become the reasons for how the software is to be structured; the requirements influence the architecture choice for the system and/or the high level requirements posed as software elements require interaction, which is defined in the architectural design of the system. The role of requirements in detail design is more direct than in architectural design. There is a one-to-one mapping between each functional requirement and a module in detail design. Page: What does aggregation mean in OO? Give an example. Ans: Aggregation is a “part-of” association. For example, student is a part of a class. Page: When we employ the technique of generalization in design, what are we doing, and which part of OO design is closely related to this concept? Ans: Generalization is an abstraction where we keep only the essentials and suppress the details. In OO, in moving from specific objects to a general class definition is an example of generalization. Page: 150

20 4. List two differences between the state transition diagram and the sequence diagram. Ans: State diagram shows the states of the objects and how those states change. Sequence diagram only shows the message interactions among the objects. Page: and Appendix C page Mention and describe three different views used in architectural design. Ans: Architectural design is a high level view of the system. It can be described with: logical view : represents the decomposition of a system and how those parts work with each other physical architectural view: represents the mapping of the software to the hardware process view: represents the run-time “processes” and flow of the system. Page: What is the difference between data modeling and logical data base design? Ans: In data modeling we are constructing and showing the Entity-Relationship among the objects. In logical data base design, the E-R diagram is converted to the sets of tables and relationships among the tables. Page:

21 7. Describe the difference between low fidelity and high fidelity prototyping in the design of the interface. Choose one and give the reasons why you would show the client this prototype. Ans: Low fidelity prototypes are quick hand drawn screens using markers, post-it notes, post cards, and/or cut out images to represent the screens of the system. They can be simple mockup sketch of the target product, as seen in page 153, Figure High fidelity prototypes are screens created using a tool to design the screens. These screens look and mimic the behavior of the future screens of the system. An example of a tool is visual basic with the use of hide and show. High fidelity prototyping is the activity of creating detailed mockup screens resembling and behaving close to the final product. Choice: Low fidelity prototyping activity is used during early stages of the system development to validate with the client/user the correctness of understanding of the system. Low fidelity prototypes can be drawn quickly to present and obtain approval from the client or user of the system. Choice: High fidelity prototype would be shown to the client/user of the system during the detail designing activity. The high fidelity prototype would show the look and feel of the proposed interface and the functional behavior of the system to the client/user at a time where changes can be incorporated. Page:

22 8. Explain the three columns in Figure 7.26 called User, Screen Output and Process with regard to design. Ans: First column – User: This column shows the user’s interaction with the system The user “aStudent” sees the system’s display “Registration” and using the drop box “All Courses” object, they select a course and click the button “Add Course”. The last interaction is the response from the system with the new screen “Registration” with a course added “SWE 2313 Intro to Software Engineering”. Second column – Screen Output: This column shows the two screens displayed by the system in this interaction. The second screen is the reaction to the user’s usage of the drop box (a scrollable list of the available courses with the user selecting in this case “SWE 2313 Intro to Software Engineering”). The screen shows the course selected with new functions: Delete course, Add another course, and Confirm Schedule. Third column – Process: The inner system process is shown as a sequence diagram. The user’s input would trigger the RegistrationGUI object to pass the registration information to the aSection object. This aSection object needs to check if the student has the prerequisites for the course. If the boolean returned is True then the message Add(aStudent) is sent to students object. Note: another sequence diagram would represent Boolean = False. Page: 156

23 9. Choose one of the cognitive models and explain how the model impacts the design of the user interface. Ans: Norman’s cognitive model impacts the design of the user interface to be more “intuitive”. The user has a mental model of the task. This mental model is the user’s common thought process (cognition-thinking). Design of an interface that looks and gives feedback resembling the common thought process of the user is an “intuitive” user interface. GOMS model promotes consideration of many basic Operators and Methods to achieve the user’s goals in the design of the user interface. Page: Visit a web site that is from a different country or culture. Give an example of a multicultural issue you found in the site. Explain how you would propose to redesign to take into consideration the issue found. Ans: Variety of web sites with URL that may be different from the common practices (.com.org.edu). The multicultural issues will include localized versions of language, colors, icons, and expression. Page: 157