The analysis steps. Problem Analysis Sub-problem 3 Sub-problem 2 Sub-problem nSub-problem 1.

Slides:



Advertisements
Similar presentations
Modern Systems Analyst and as a Project Manager
Advertisements

CS 325: Software Engineering January 13, 2015 Introduction Defining Software Engineering SWE vs. CS Software Life-Cycle Software Processes Waterfall Process.
ATTENTION This presentation breaks down the purchasing process into 6 steps, which are then detailed in the subsequent slides. While responding from either.
Chapter 1 4th Edition What is Software Engineering Shari L. Pfleeger
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
What is software engineering?
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne. – Times: –See noticeboard outside.
Administrative Topics -TEACH/mailing list - Brainstorm - Pick a project manager for each HW assignment (responsible for communication, scheduling and execution.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
CSC230 Software Design (Engineering)
Software Engineering (Chapter 15 in text). Science vs. Engineering The difference between science and engineering:  Science seeks to explain phenomena.
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Managing Software Quality
Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Pertemuan 5 Pengembangan Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Information Systems Chapter 10 – Computers: Understanding Technology, 3 rd edition 1November 13, 2008.
What is software? Software is a set of items or objects that form a configuration that includes: –Programs –Documents –Data.
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
IT Requirements Management Balancing Needs and Expectations.
Software Requirements Engineering: What, Why, Who, When, and How
Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.
Basic of Software Testing Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
CS361 Software Engineering I
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
What is Software Engineering? The discipline of designing, creating, and maintaining software by applying technologies and practices from computer science,
Software quality factors
Chapter 1 Quality terminology Error: human mistake Fault: result of mistake, evidenced in some development or maintenance product Failure: departure from.
1 EE29B Feisal Mohammed EE29B: Introduction to Software Engineering Feisal Mohammed Ph: x3156.
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
Quality Factors Chapter Three. Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
CHAPTER 2 TYPES OF BUSINESS INFORMATION SYSTEM. INTRODUCTION Information System support business operations by processing data related to business operation.
Database Systems. Role and Advantages of the DBMS Improved data sharing Improved data security Better data integration Minimized data inconsistency Improved.
CMSC 345 Fall 2000 Software Design and Development.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Software Engineering. Acknowledgement Charles Moen Sharon White Bun Yue.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Margaret Christison Head of Product Data Standards Product Information Standards Defence Logistics 2004.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Metrics "A science is as mature as its measurement tools."
HNDIT23082– Principals of Software Engineering
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
Chapter 1 SOFTWARE ENGINEERING What is Software Engineering.
Software development techniques in Albanian private software companies Arbora Dalaci, Esmeralda Kapcari
 System Requirement Specification and System Planning.
Lecture 9 - Business Information Systems: Electronic Business Systems
Rekayasa Perangkat Lunak Part-10
Rekayasa Perangkat Lunak
Software Quality Assurance Software Quality Factor
Topic for Presentaion-2
مقدمه اي بر مهندسي نيازمنديها
Rekayasa Perangkat Lunak
Software Quality Engineering CS- 449
Introduction to Software Testing
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Presentation transcript:

The analysis steps. Problem Analysis Sub-problem 3 Sub-problem 2 Sub-problem nSub-problem 1

The process of analysis. Solution Solution 3 Solution 4 Solution 2 Solution 1 Proposed solution types…..

The relationship between computer science and software engineering Computer ScienceCustomer Theories Computer Functions Problem Type Software Engineering Tools and Techniques to Solve Problem

How human error causes a failure. Human ErrorFaultFailure can lead to

McCall’s quality model. Correctness Reliability Efficiency Integrity Usability Maintainability Testability Flexibility Portability Reusability Interoperability Traceability Completeness Consistency Accuracy Error Tolerance Execution Efficiency Storage efficiency Access control Access audit Operability Training Communicativeness Simplicity Conciseness Instrumentation Self-descriptiveness Expandability Generality Modularity Software System Independence Machine Independence Communications commonality Data commonality

CUSTOMER Sponsors system development USER Uses system PROGRAMMER Builds system Contractual obligation Software system Needs Participants in software development.

System definition of paycheck production. System boundary Computer Mail room Date validation Calculation Pay checks Printing Pay information

Layers of a water-monitoring system. Remote data collection system Reporting system for data Calculation system for remote data Communication system from remote sites to central Data management system for collected data

The roles of the development team Maintenance System Design Requirements Analysis and Definition Program Design Program Implementation Unit Testing Integration Testing System Testing System Delivery SOFTWARE DEVELOPMENT STEPS DEVELOPER ROLES ANALYST DESIGNER PROGRAMMER TESTER TRAINER

The key factors that have changed software development Time to market Shifts in economics Desktop computing Networking Object technology Problems with waterfall User interfaces CHANGES IN SOFTWARE ENGINEERING

Electrical device Sensor Water sensorAir sensor Simple Hierarchy for monitoring equipment Example

Differences in development (Wasserman 1996). Controlled development Rapid application development Mission-critical Multiuser Multiplatform 2- to 3-tier development Limited scope/vision Low/medium risk Single/multiplatform 1- to 2-tier development Packages/minimal development Lowcost/low risk Single platform Single-user, desktop productivity tools Departmental applications Enterprise- or division-wide applications

Using measurement to fid a solution Real, Empirical WorldFormal, Mathematical World Empirical relational system Formal relational system Empirical relevant results Numeric Results Implementation of solution Interpretation Measurement Mathematics, statistics

Piccadilly Television franchise area. Example

Figure1.17 Piccadilly context diagram showing system boundary. (Robertson and Robertson). Piccadilly Television Airtime Sales Production Companies Piccadilly Management Broadcasting Board Program Suppliers Suggested Campaign New Program Television Ratings Report Program Purchase Agreement Agreed Campaign Advertising Agencies Selected Spots Spot Upgrade Request Campaign Requirements Copy Transmission Instructions Program Transmission Schedule Agency Invoice Ratecard Preemption Warning Commercial Copy Recording Sales Target Instructions Revenue Reports Program Transmission Schedule Programming Rules Audience Measurement Bureaus Upgrade confirmation