7 Million Study Materials
From students who've taken these classes before
From students who've taken these classes before
24/7 Access to Tutors
Personal attention for all your questions
Personal attention for all your questions
Learn
93% of our members earn better grades
93% of our members earn better grades
Georgia Tech | CS 3300
Intro To Software Engr
Professors
- Orso Leach
100 sample documents related to CS 3300
-
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Fall 2008 Alessandro (Alex) Orso http:/www.cc.gatech.edu/~orso Before we start Whats your background? Alex Orso - CS 3300 1 General Information See classs website: http:/www.cc.gatech.edu/classes/AY2009/cs3300 -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 03: Project planning The project scheduling process Alex Orso - CS 3300 1 Activity organization Activities in a project should be organised to produce tangible outputs for management to judge progress Mi -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 04: Tools day #1: Eclipse, CVS, DB Eclipse Install Eclipse (http:/www.eclipse.org) Set up a new project in Eclipse Workspace and project structure The Java perspective Using the project wizard Creating p -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 04 : Software Requirements Team Work Reminder: Process activities Software specication Software design and implementation Software validation Software evolution Alex Orso - CS 3300 1 Software specication -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 05 : Feedback on Project Plan Software Design Software Design 1 Software design System organization that satises functional and non-functional requirements Input: Specication what to do Output: Design -
Georgia Tech CS 3300
So#wareProcess Therelatedsetofac2vi2esandprocessesthatare involvedindevelopingandevolvingaso#waresystem Summerville Aseriesofstepsorganizedtoachieveagoal RealWorldSo:wareProcess 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. OrdertheTshirtsforthedevelopmentteam Announc -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 07 : Software Testing Acknowledgements: Andreas Zeller provided some of the material used in these slides Software Testing Functional and Structural Testing 1 Functional vs. Structural Testing Fu nc ti on -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 09 : Alternative verication techniques Debugging Static and dynamic verication Dynamic verication: Concerned with exercising and observing SW behaviour The system is executed with test data and its opera -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 12 : eXtreme Programming XP XP is a lightweight methodology for small to medium sized teams developing software in the face of vague or rapidly changing requirements. - Kent Beck 1 What is XP? XP is a Lig -
Georgia Tech CS 3300
Todays Topics 2 The potential of Ajax GWT brings software engineering to Ajax Focus on the user and all else will follow Fast is better than slow Wrap-up Q&A Copyright 2007 Google Inc. The Status Quo 3 Browsers are treated like HTML dumb terminals Everyth -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 14 : Unit Testing, Tools, and Exercise Why is unit testing important? Imposes developers discipline Provides incremental specication Avoids regression errors Allows for changing with condence Its all abou -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 15 : Refactoring (slides from Frank Tip and Sunil Manoharan) Refactoring refactoring is the process of applying transformations (refactorings) to a program, with the goal of improving its design without c -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Class 16 : Design Patterns History of (Design) Patterns In 1977, Christopher Alexander (Emeritus Professor of Architecture at UC Berkeley) introduces the idea of patterns: C. Alexander, S. Ishikawa, M. Silverst -
Georgia Tech CS 3300
CS3300 Introduction to Software Engineering Topic : Final Review Individual Contributions Complete them by the day of the nal (the sooner, the better) Alex Orso - CS 3300 1 Topics (I) General SE principles Project planning The software process Requireme -
Georgia Tech CS 3300
MidTerm Death Trip Key CS3300 2/28/06 -Name (1pt) 1. Develop an architectural description of the system. What architectural patterns does it include? (33pts) Architectural Description (22pts) Architectural Patterns (11pts) Architectural Description: -
Georgia Tech CS 3300
Capability Maturity Model Process Assessment Capability Maturity Model (CMM) (Section 3 from SEI TR) and follow-up CMMI (Chapter 28) Assessment process Developed by the Software Engineering Institute (SEI) with DoD funding Designed for large or -
Georgia Tech CS 3300
Management Early Communication Key to Software Project Success Ware Myers Inception Because the first phases of development are upstream activities that affect all that follows, they\'re vital to overall project success. It\'s foolish, for example, t -
Georgia Tech CS 3300
CS3300: Introduction to Software Engineering www.cc.gatech.edu/classes/AY2006/cs3300_fall Ada Gavrilovska (ada@cc) CCB 222, MW 1-2pm (may change) reading assignments midterm and final (20% + 20%) class participation project (55%) you cho -
Georgia Tech CS 3300
CS 3302 Configuration Management Cases Case 3: Fixes Unfixed Dan and Joan are both working on an enhancement to Burdell Inc.\'s personnel database software. They have made personal copies of the software to work on so that any changes that they make -
Georgia Tech CS 3300
Quality Management Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 27 Slide 1 Objectives q q q q To introduce the quality management process and key quality management activities To explain the role of standards in quality man -
Georgia Tech CS 3300
Importance of UI Design System users often judge system quality by its interface rather than its functionality User Interface Design Chapter 16 +. Computers are now being used by many non-technical people Implementers are often poor judges of -
Georgia Tech CS 3300
CS 3300 Software Engineering Colin Potts Fall, 2000 What is Software Engineering? s An Exercise: List all the ways in which s s s Building a tinkertoy car for fun is different from designing a new automobile Building a treehouse is different from -
Georgia Tech CS 3300
Agile methods Agile methods, XP and test-driven development Ch. 17.1 and 17.2 Dissatisfaction with the overheads involved in design methods led to the creation of agile methods. These methods: Focus on the code rather than the design; Are based -
-
Georgia Tech CS 3300
The software process A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. Generic software process models The waterfall model Separate and distinct phases of specification and d -
Georgia Tech CS 3300
Soft E Test 2 CS 3300 6/30/03 By putting your name on this paper you agree to the terms of the Georgia Tech Honor Code Nombre_ Consider the following problem. Your group\'s task is to design and implement a testing tool that tests the programs of othe -
Georgia Tech CS 3300
Requirements Requirements Chapters 6 and 7 see SRS template for next submission A requirement is a property of the system being constructed high-level business, functional- or non-functional, interface, properties It is generated by the custo -
Georgia Tech CS 3300
Exercise ( 1) ( 2) C ( 3) ( 4) ( 5) ( 6) ( 7) ( 8) ( 9) (10) (11) (12) (13) DOUBLE PRECISION FUNCTION SIN(X, E) THIS DECLARATION COMPUTES SIN(X)TO ACCURACY E DOUBLE PRECISION E,TERM,SUM REAL X TERM=X DO 20 I=3,100,2 TERM=TERM*X*2/(I*(I-1) IF(TERM.LT. -
Georgia Tech CS 3300
Cleanroom attempt to mathematically-based, scientific engineering process of software development \"Cleanroom software engineering yields software that is correct by mathematically sound design, and software that is certified by statistically-valid -
Georgia Tech CS 3300
Case Study Software to support a video store Track rentals; print reports Refactor to improve design (code handouts given in class) Movie 1 Class Diagram Rental Customer priceCode: int * daysRented: int * 1 statement() Interaction Diagram -
Georgia Tech CS 3300
Configuration Management A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record an -
Georgia Tech CS 3300
Demo Grading Criteria Team: Projects with associated UIs 1. Functionality 2. Correctness (Quality) 3. User Interface TOTAL DOCUMENT GRADE *Possibility of receiving 20 percentage points. Projects without associated UIs 1. Functionality 2. Correctness -
Georgia Tech CS 3300
7. UNIT TESTING Software Engineering Roadmap: Chapter 8 Focus Identify corporate practices Plan project Analyze requirements Design Implement Test units Maintain Integrate & test system Test units (parts) separately - use implementations - apply di -
Georgia Tech CS 3300
Pr ogr am Analysi s CS2335 Spr i ng 2002 Agenda Contr ol Fl ow Gr aphs Data Fl ow Gr aphs M cCabe M easur e H al stead M easur e Why do Pr ogr am Anal ysi s? Esti mate Compl exi ty of modul es (M cCabe) Esti mate Er r or s (H al stead) Se -
Georgia Tech CS 3300
5. DESIGN I: SOFTWARE ARCHITECTURE Software Engineering Roadmap: Chapter 5 Focus Develop Architecture Identify corporate practices Plan project Analyze requirements Design Implement Test units Adapted from Software Engineering: An Object-Oriented Pe -
Georgia Tech CS 3300
Classic Mistakes People: 1. Undermined motivation 2. Weak personnel 3. Uncontrolled problem employees 4. Heroics 5. Adding people to a late project 6. Noisy, crowded offices 7. Friction between developers and customers 8. Unrealistic ex -
Georgia Tech CS 3300
Software Requirements Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 6 Slide 1 Objectives q q q To introduce the concepts of user and system requirements To describe functional and non-functional requirements To explain how so -
Georgia Tech CS 3300
<?xml version=\"1.0\" encoding=\"UTF-8\"?> <Error><Code>InternalError</Code><Message>We encountered an internal error. Please try again.</Message><RequestId>D68642D7F466DB83</RequestId><HostId>gsely4Ow8/aYL/Svl2bIp1n0S1+Arupw0KwcqTcqMUjFniuqerKdW4HRywEVA -
Georgia Tech CS 3300
Why Design Design Chapters mainly 8 and 11 (for now) sds.doc look at grading criteria as well good design -> good code easier to code, test, maintain, change easier to understand impact of requirements changes large projects divide across -
Georgia Tech CS 3300
System models Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 8 Slide 1 Objectives q q q q To explain why the context of a system should be modelled as part of the RE process To describe behavioural modelling, data modelling a -
Georgia Tech CS 3300
Architectural Design Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 11 Slide 1 Objectives q q q q To introduce architectural design and to discuss its importance To explain the architectural design decisions that have to be m -
Georgia Tech CS 3300
Software testing Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 1 Objectives q q q q To discuss the distinctions between validation testing and defect testing To describe the principles of system and component testin -
Georgia Tech CS 3300
Verification and Validation Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1 Objectives q q q q To introduce software verification and validation and to discuss the distinction between them To describe the program ins -
Georgia Tech CS 3300
Describe product and status of development Introduction of team Team name, team members, their roles Product to be delivered Presentations and Demos 15min per team LEAVE room for Q&A, 3 teams per period you will not know your exact order, b -
Georgia Tech CS 3300
Quality Management Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 27 Slide 1 Objectives q q q q To introduce the quality management process and key quality management activities To explain the role of standards in quality man -
Georgia Tech CS 3300
Object Oriented Development Object Oriented Design and Model Driven Architecture Chapter 14 (somewhat) object oriented analysis object oriented design object oriented programming think in terms of objects which encapsulate structure, behavior, -
Georgia Tech CS 3300
Object-oriented Design Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 14 Slide 1 Objectives q q q q To explain how a software design may be represented as a set of interacting objects that manage their own state and operation -
Georgia Tech CS 3300
Delivery Grading Criteria Installation Manual: external software system identifies, download location, version number? installation procedure? Design Followed: Is the architecture visible in the source code structure? Are the classes from the l -
Georgia Tech CS 3300
Project Plan Grading Criteria Team Name: 1. Introduction Overview 5 Deliverables 5 Assumptions 5 2. Management Data Lifecycle Selection 5 Team Member Role Assignment 3. Planning and Control Project Estimate 5 Milestones 5 Work Breakdown 10 Project Sc -
Georgia Tech CS 3300
CS 3300 - PROJECT CONTRIBUTIONS I would like each member of the team to give me a description of their contributions to the project. In particular, please use the format given below. Please email me or give me hard copy of your -
Georgia Tech CS 3300
User interface design Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 16 Slide 1 Objectives q q q q q To suggest some general design principles for user interface design To explain different interaction styles and their use To -
Georgia Tech CS 3300
Delivery Grading Criteria Team: 1. Release Notes 2. Installation Instructions 3. Man Page 4. User Document 5. Source Code TOTAL DOCUMENT GRADE 15 15 15 30 25 100 1. Does the delivery contain release notes that include outstanding bugs? 2. Are instal -
Georgia Tech CS 3300
Software Process Models CS3300 Contents Software process phases s Software lifecycle models s s s s s s Build and fix model Waterfall model Rapid prototyping Incremental model Spiral model Work-breakdown structure s Project planning (intro) s Pr -
Georgia Tech CS 3300
[ Project ] Software Design Specification Draft X January 29, 2005 [ Team Name ] [ Paste Your Team\'s Logo Here ] [Paste your logo here] [ Team Name ] [ Project ] - Software Design Specification Revisions Version Draft Type and Number Primary Aut -
-
Georgia Tech CS 3300
Project Management Concepts People - Categories Senior managers business issues Technical managers technical issues Practitioners technical skills Customers specify requirements End users interact with software Team Leaders Difficult ski -
Georgia Tech CS 3300
6. DESIGN II: DETAILED DESIGN Develop Architecture - see chapter 5 Identify corporate practices Plan project Analyze requirements Design Implement Software Engineering Roadmap: Chapter 6 Focus Perform Detailed Design - apply design patterns - acco -
Georgia Tech CS 3300
First Exam CS 3300 6/10/03 Nombre _ I don\'t care if you use your book or notes. I want you to think, not recite facts. By putting your name on this exam you are agreeing to the policies of the honor code of Georgia Institute of Technology. The proje -
Georgia Tech CS 3300
UML Class Diagrams CS3300 Fall 2002 Agenda Lecture Symbology Basic Modeling Intermediate Modeling Class Diagrams A class diagram shows: Classes Attributes Methods A class diagram is a STATIC view of system Interfaces Collabo -
Georgia Tech CS 3300
Design Document Grading Criteria Team: 1. Introduction 2. Design Considerations 3. Software Architecture Description 5 Rationale 5 4. Component Design Static Models 10 Dynamic Models 10 5. Low Level Design Static Models 10 Dynamic Models 10 6. User I -
Georgia Tech CS 3300
Things We Do = Set Speed # - Speed of vehicle is passes into the system, along with a memory # to which to store the speed setting. If there is no memory funtion, then the speed setting is set to a default (1) location. When the speed is set, the cr -
Georgia Tech CS 3300
An Introduction to Software Engineering Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1 Objectives q q q To introduce software engineering and to explain its importance To set out the answers to key questions about so -
Georgia Tech CS 3300
Rapid software development Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1 Objectives q q q q To explain how an iterative, incremental development process leads to faster delivery of more useful software To discuss -
Georgia Tech CS 3300
CS3300 SOFTE Third Exam 7/14/03 Remember the honor code. Open book and notes. Nombre_ 1.The inspection process we presented and had you practice could be called a white-box inspection. In other words, you inspected for correctness. How would you cond -
Georgia Tech CS 3300
CS 3300 Configuration Management Cases Case 1: Year 2000 The IS Division of Burdell Inc. has an automated payroll system and is beginning to automate other business operations. In early 1999, Eric Whizz, the chief programmer of the accounts payable -
Georgia Tech CS 3300
CS 3300, Assignment 2 Due: Wed. Nov., 29 Answer the question that relates to the class project that you are familiar with (this supersedes previous instructions given in class). 1. (SLR Camera) The camera you have considered so far does not support a -
Georgia Tech CS 3300
CoLab Deliverable Two CS 3300 Group Seven Liem, Johannes Luongo, Matt Martin, Chris Overman, Pamela April 1, 2008 Summary of Document Changes From D1 Product Overview Delivery Description Design Overview Design Detail No change Covers D2 delivere -
Georgia Tech CS 3300
CoLab DeliverableThree CS3300 GroupSeven Liem,Johannes Luongo,Matt Martin,Chris Overman,Pamela April21,2008 SummaryofDocumentChangesFromD2 ProductOverview DeliveryDescription DesignOverview DesignDetail DesignUML DataDesign InterfaceSpecification -
Georgia Tech CS 3300
Design Document Grading Criteria Team: 1. Introduction 2. Design Considerations 3. Software Architecture Description 5 Rationale 5 4. Component Design Static Models 10 Dynamic Models 10 5. Low Level Design Static Models 10 Dynamic Models 10 6. User I -
Georgia Tech CS 3300
Final Presentation Grading Criteria CS 3911b Fall 2004 Team: Speakers: Content Project Goal/Vision Key Requirements & Design Elements Accomplishments Plan vs. Reality Reflection/Lessons Learned Demo Organization/Walkthrough Quality Delivery Languag -
Georgia Tech CS 3300
MidTerm Status Presentation Grading Criteria CS 3911b Fall 2004 Team: Speakers: Content Problem Statement Schedule Status Resource Status Accomplishments Issues/Risks/Showstoppers Delivery Language & Style Explanation of Technical Material Eye Conta -
Georgia Tech CS 3300
Project Plan Grading Criteria Team Name: 1. Introduction Overview 5 Deliverables 5 Assumptions 5 2. Management Data Lifecycle Selection 5 Team Member Role Assignment 3. Planning and Control Project Estimate 5 Milestones 5 Work Breakdown 10 Project Sc -
Georgia Tech CS 3300
CS3911 PEER EVALUATION FORM NAME: _ TEAM#:_ DATE: _ MIDTERM / FINAL Work Difficulty For each team member (include yourself) rate relative % and diffculty NAME Work Required (Role) TOTAL (100%) Rate the overall team (1 = inadequate, 5 = superior) Te -
Georgia Tech CS 3300
1. The Context of Software Engineering Definition of \"Engineering\" The profession in which a knowledge of the mathematical and natural sciences gained by study, experience, and practice . - Accreditation Board for Engineering and Technology Defini -
Georgia Tech CS 3300
Colin Potts, 3302 Winter 1997 Exercise: Three Problems l Get Configuration Management Colin Potts CS 3300 l Reading into groups of three the cases Individually read one of the cases and answer the questions that follow it Describe the case and -
Georgia Tech CS 3300
4x Size (SLOC) + Cost ($) RELATIVE SIZE RANGE 2x 1.5x 1.25x x + + + + + + 0.5x + Product Concept of Requirements design operations specification specs. Feasibility Plans and requirements Product design Detailed design specs. + + + + + Software Co -
Georgia Tech CS 3300
Software Engineering Roadmap: Chapter 1 Focus PROCESS (Pass 1) GA Tech CS 3300 AY 2002 Fall 2001 Identify corporate practices - assess capability - specify standards - e.g. CMM level Plan configuration management - how to manage documents & code - -
Georgia Tech CS 3300
REQUIREMENTS ANALYSIS (Customer Perspective) GA Tech CS 3300 AY 2002 Fall 2001 Chapter Learning Goals Distinguish C- (Customer) requirements from D- (Detailed) requirements Be equipped with ways to express C-requirements exploit use cases explo -
Georgia Tech CS 3300
The Activities of Software Engineering GA Tech CS 3300 AY 2002 Fall 2001 Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. Contents The Four P\'s of Software Engineering Process -
Georgia Tech CS 3300
PROJECT MANAGEMENT (Pass 1) GA Tech CS 3300 AY 2002 Fall 2001 Software Management Engineering structure Roadmap: - hierarchical, peer,. Chapter 2 Focus Corporate practices Plan project Analyze requirements Design Implement Development phases Risk i -
Georgia Tech CS 3300
CS 3300: Software Engineering Fall, 2001 Final Exam (Take-home) Due: Friday, December 14, 2001. 11a.m. The final is due by 11am on Friday, December 14th. Jay will be sitting in the CCB picnic area waiting for your final from 10am until 10:59:59am on -
Georgia Tech CS 3300
CS 3300 Fall, 2001 Individual Assignment Due Thursday, November 15 in class Answer all questions. Each question is worth the same number of points. The first two questions consist of two parts. The first part consists of a question/answer pair (marke -
Georgia Tech CS 3300
Contents The Four Ps of Software Engineering Process People Project Product The Activities of Software Engineering GA Tech CS 3300 AY 2002 Fall 2001 Non-Contents Assignments and Project deadlines. (Next Tuesday) Quality Project Work Domain -
Georgia Tech CS 3300
Agenda Types of maintenance Maintenance planning, and the maintenance (or change) request MAINTENANCE GA Tech CS 3300 AY 2002 Fall 2001 Typical change requests and the management of their flow Technical impacts of change requests Metrics, and -
Georgia Tech CS 3300
Getting their name right: (1/1) Question 1: 50 pts, part A 25, part B 25. 1A) Level 1: 15 pts. (L1) -Justification of what was lacking -10PTS (L1A) Level 2: 5 pts (L2) - Functionality of product is documented - 5pts (L2A) -
Georgia Tech CS 3300
8. SYSTEM INTEGRATION Software Engineering Roadmap: Chapter 9 Focus Identify corporate practices Plan project Analyze requirements Design Implement Test units Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley -
Georgia Tech CS 3300
The Activities of Software Engineering GA Tech CS 3300 AY 2002 Fall 2001 Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission. Contents The Four P\'s of Software Engineering Process -
Georgia Tech CS 3300
PROCESS (Pass 1) GA Tech CS 3300 AY 2002 Fall 2001 Software Engineering Roadmap: Chapter 1 Focus Identify corporate practices - assess capability - specify standards - e.g. CMM level Plan configuration management - how to manage documents & code - -
Georgia Tech CS 3300
2 PROJECT MANAGEMENT Software Engineering Roadmap: Chapter 2 Focus Corporate practices Plan project Analyze requirements Design Implement Test units Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), wi -
Georgia Tech CS 3300
Chapter Learning Goals REQUIREMENTS ANALYSIS (Customer Perspective) GA Tech CS 3300 AY 2002 Fall 2001 Distinguish C- (Customer) requirements from D- (Detailed) requirements Be equipped with ways to express C-requirements exploit use cases explo -
Georgia Tech CS 3300
3 REQUIREMENTS ANALYSIS I Software Engineering Roadmap: Chapter 3 Focus Obtain customer\'s wants and needs (C-requirements) Express C-requirements prose use cases state diagrams data-flow diagrams Maintain Integrate & test system Implement Test units -
Georgia Tech CS 3300
Chapter Learning Goals Understand \"Software Architecture\" term SOFTWARE ARCHITECTURE DESIGN (Pass 1) GA Tech CS 3300 AY 2002 Fall 2001 Utilize frameworks, design patterns, and models Develop architecture alternatives Relate architectures to det -
Georgia Tech CS 3300
PROJECT MANAGEMENT (Pass 1) GA Tech CS 3300 AY 2002 Fall 2001 Software Management Engineering structure Roadmap: - hierarchical, peer,. Chapter 2 Focus Corporate practices Plan project Analyze requirements Design Implement Development phases Risk i -
Georgia Tech CS 3300
4 REQUIREMENTS ANALYSIS II Software Engineering Roadmap: Chapter 4 Focus Identify corporate practices Plan project Analyze requirements Design Obtain C-Requirements (previous chapter) Obtain D-requirements - unambiguous - traceable - atomic - test -
Georgia Tech CS 3300
Problem #1: 25 points The resulting requirement specification fragment must specify: 1. Input a. Names of the People - 5 pts b. Entry/Retrieval of each person\'s available time(s): 5 pts 2. Calculation of shared free time: 5 pts 3. Outpu -
Georgia Tech CS 3300
Socio-technical Systems Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 2 Slide 1 Objectives q q q q q To explain what a socio-technical system is and the distinction between this and a computer-based system To introduce the -
Georgia Tech CS 3300
Critical Systems Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 3 Slide 1 Objectives q q q To explain what is meant by a critical system where system failure can have severe human or economic consequence. To explain four dimen -
Georgia Tech CS 3300
User interface design Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 16 Slide 1 Objectives q q q q q To suggest some general design principles for user interface design To explain different interaction styles and their use To -
Georgia Tech CS 3300
V-model again Design Validation when can you assess a design? Requirements Requirements Designs don\'t run analysis analysis Acceptance/ Acceptance/ reqts validn. reqts validn. LHS -> RHS LHS -
Georgia Tech CS 3300
The final requirement for the semester includes scheduling a meeting of the whole project team with the customer. Attendance by the faculty advisor at this meeting is strongly encouraged, but not required. The agenda for this meeting should include:
7,000,000 study materials • 24/7 tutors • earn better grades