GROUP MEMBERS NAME ROLL NO SHAUBAN ALI 17-ARID-5650 UMAIR MUSHTAQ 17-ARID-5656 TARIQ SAEED 17-ARID-5657 MUSKAN WADOOD 17-ARID-5641.

Slides:



Advertisements
Similar presentations
The Architecture Design Process
Advertisements

©Ian Sommerville 2000Software Engineering, 6th edition Slide 1 Introduction l Getting started with software engineering l Objectives To introduce software.
Software Engineering General Project Management Software Requirements
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Socio-technical Systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Systems engineering 1.
Control environment and control activities. Day II Session III and IV.
Chapter 10 – Sociotechnical Systems 1Chapter 10 Sociotechnical Systems.
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering As modified by Randy Smith.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
This chapter is extracted from Sommerville’s slides. Text book chapter
Socio-technical Systems (Computer-based System Engineering)
Lecture 7: Requirements Engineering
Managing people l Managing people working as individuals and in groups.
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
Chapter 5 – System Modeling Lecture 9 Section A 27/4/2015 Section B 29/4/2015 1Chapter 5 System modeling.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Introduction to OOAD and UML
CHAPTER 2. Designing, implementing, deploying and operating systems which include hardware, software and people.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Project Execution Methodology
Chapter 5 – System Modeling
CompSci 280 S Introduction to Software Development
IT Service Transition – purpose and processes
CompSci 280 S Introduction to Software Development
CompSci 280 S Introduction to Software Development
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Classifications of Software Requirements
Chapter 5 System modeling
Chapter 4 – Requirements Engineering
Chapter 4 Requirements Engineering (1/3)
Chapter 4 – Requirements Engineering
Chapter 5 – Requirements Engineering
Chapter 5 – System Modeling
The Development Process of Web Applications
Chapter 6: Database Project Management
Quality Management chapter 27.
Architecture Concept Documents
Unified Modeling Language
Software Engineering B.Tech Ii csE Sem-II
System Design and Modeling
Chapter 5 – System Modeling
Security Engineering.
System Modeling Chapter 4
Abstract descriptions of systems whose requirements are being analysed
IS301 – Software Engineering V:
Process Diagram Technique for Business Processes Modeling
System models October 5, 2005.
Chapter 2 – Software Processes
Object Oriented Analysis and Design
Chapter 6 – Architectural Design
Chapter 9 – Software Evolution and Maintenance
Design and Implementation
Chapter 13 Quality Management
CS310 Software Engineering Dr.Doaa Sami
Chapter 22 – Project Management
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Chapter 8 Software Evolution.
Network Architecture By Dr. Shadi Masadeh 1.
Requirements Document
Chapter 5 Architectural Design.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 4 System Modeling.
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Presentation transcript:

GROUP MEMBERS NAME ROLL NO SHAUBAN ALI 17-ARID-5650 UMAIR MUSHTAQ 17-ARID-5656 TARIQ SAEED 17-ARID-5657 MUSKAN WADOOD 17-ARID-5641

COMPUTER BASE SYSTEM ENINEERING MANAGEMENT SYSTEM SYSTEM AND THEIR ENVIRONMENT SYSTEM MODELING SYSTEM EMERGING PROCESS

What is a System? Complex: Restricts the definition to systems in which the elements are diverse have intricate relationships with one another

system A system may include software, mechanical, electrical and electronic hardware and be operated by people. System components are dependent on other system components

Definitions of SE Designing, implementing, deploying and operating systems which include hardware, software and people

What is a management system? A management system is the way in which an organization manages the inter-related parts of its business in order to achieve its objectives. These objectives can relate to a number of different topics, including product or service quality, operational efficiency, environmental performance, health and safety in the workplace and many more.

Risk Management Risk management is one of the most important jobs for project manager. You can think of a risk as something that you’d prefer not have to happen. Risk may threaten to project, the software that is being developed,or the organization.

Risk Management Risk identification you should identify possible project, product, and business risks. Risk analysis You should access the likelihood and consequences' of these risk Risk monitoring You should regularly assess the risk and you plans for risk mitigation and revise these plans when you learn more about the risk

Managing people The people working in a software organization are its greatest assets. It is expensive to recruit and retain good people, and it is up to software managers to ensure that the engineers working on a project are as productive as possible. It is important that software project managers understand the technical issues that influence the work of software development. There are four critical factors that influence the relationship between a manager and the people that he or she manages. Consistency Respect peoples Inclusion people contribute effectively Honesty as a manager

Motivating people As a project manager, you need to motivate the people who work with you so that they will contribute to the best of their abilities

Team work Most professional software is developed by projects teams that range in size form two to several hundred people. However, as it is impossible for everyone in large group to work together on a single problem. Large teams are usually split into a number of smaller groups. Each group is responsible for devolving part of over all system. The best size for a software engineering group is 4 to 6 members. When group small, communication problems and reduced. Everyone knows everyone else, and the whole group can get around a table for a meeting to discuss the project and the software and they are devolving. The group can establish its own quality standard Individuals learn from and support each others Refactoring and continual improvement is encouraged

Systems and their environment Systems are not independent but exist in an environment System’s function may be to change its environment Environment affects the functioning of the system e.g. system may require electrical supply from its environment The organizational as well as the physical environment may be important

System Modeling System modeling helps the analyst to understand the functionality of the system and models are used to communicate with customers l Different models present the system from different perspectives External perspective showing the system’s context or environment Behavioral perspective showing the behavior of the system Structural perspective showing the system or data architecture

System modelling Presented as a block diagram showing the major sub-systems and interconnections between these sub-systems May include major information flows between sub-systems May identify different types of functional component in the model

Context models Context models are used to illustrate the operational context of a system - they show what lies outside the system boundaries. Social and organisational concerns may affect the decision on where to position system boundaries. Architectural models show the system and its relationship with other systems.

Structural models Structural models of software display the organization of a system in terms of the components that make up that system and their relationships. Structural models may be static models, which show the structure of the system design, or dynamic models, which show the organization of the system when it is executing. You create structural models of a system when you are discussing and designing the system architecture.

Behavioral models Behavioral models are models of the dynamic behavior of a system as it is executing. They show what happens or what is supposed to happen when a system responds to a stimulus from its environment. You can think of these stimuli as being of two types: – Data Some data arrives that has to be processed by the system. – Events Some event happens that triggers system processing. Events may have associated data, although this is not always the case.

SYSTEM EMERGING PROCESS The system emerging process, also known as the System Development Life Cycle, is a term used in the development of software where a set of methodical processes, activities, or phases are used to develop and implement a system.

SYSTEM EMERGING PROCESS Common System Development Steps A software system seeks to solve a problem. The following steps are common to most development processes and describe the general details of the steps taken to achieve this. The steps are designed to develop a system characterized by quality and accuracy, and one that reflects the client's requirements.

MAJOR STEPS Information Gathering Analysis Design Implementation Testing Deployment

EMERGING SYSTEM PROPERTIES Emergent properties are a consequence of t he relationships between system component s. They can therefore only be assessed and me asured once the components have been inte grated into a system.

EMERGING SYSTEM PROPERTIES Emergent system properties are properties of the system as a whole rather than properties that can be derived from the properties of co mponents of a system.

TYPES OF EP Functional Emergent Properties. Non-functional Emergent Properties.

TYPES OF EP FUNCTIONAL EMERGENT PROPERTIES These appear when all parts of system work together. Example A car has functional properties of being a transport device, so it Hans assembled from its component.

TYPES OF EP FUNCTIONAL EMERGENT PROPERTIES These appear when all parts of system work together. Example A car has functional properties of being a transport device, so it hans assembled from its component.

Example of emerging properties The volume of the system The reliability of the system The security of the system The reparability of the system The usability of the system