Pearson Education 2007 Chapter 1 (RASD 3/e)
|
|
- Junior Lucas
- 6 years ago
- Views:
Transcription
1 Chapter 1 (RASD 3/e) MACIASZEK, L.A. (2007): Requirements Analysis and System Design, 3 rd ed. Addison Wesley, Harlow England ISBN Chapter 1 Software Process Pearson Education Limited 2007 Topics The nature of software development System planning Systems for three management levels The software development lifecycle Development models and methods Problem statements for case studies (separate set of slides) Chapter 1 (Maciaszek - RASD 3/e) 2 MACIASZEK (2007): Req Analysis & Syst Design 1
2 Chapter 1 (RASD 3/e) 1. The nature of software development 70% of software projects fail (The Standish Group report, 2005) an exaggeration? The essence of software development defined by the issues inherent in the software itself software is a product of a creative act (not a result of a repetitive act of manufacturing) difficulties not amenable to breakthroughs or silver bullets software development invariants (constants): complexity, conformity, changeability, and invisibility. Chapter 1 (Maciaszek - RASD 3/e) 4 MACIASZEK (2007): Req Analysis & Syst Design 2
3 Chapter 1 (RASD 3/e) The accidents of software development Accidental difficulties (variables) due to software production practices amenable to human intervention attributed mostly to the fact that an information system is a social system the software solution must not be adding to the inherent complexity of the software product adaptiveness (supportability) is the challenge Related to: adaptiveness = understandability + maintainability + scalability (extensibility) Stakeholders Process Modeling Chapter 1 (Maciaszek - RASD 3/e) 5 Variable 1 - Stakeholders People who have a stake in a software project: Customers (users and system owners) Developers (analysts, designers, programmers, etc.) Information systems are social systems developed by people (developers) for people (customers) The main causes of software failure can be traced to the stakeholder factor on the customer end, and on the developer end Chapter 1 (Maciaszek - RASD 3/e) 6 MACIASZEK (2007): Req Analysis & Syst Design 3
4 Chapter 1 (RASD 3/e) Variable 2 - Software process Defines activities and organizational procedures used in software production and maintenance A process model: states an order for carrying out activities; specifies what development artifacts are to be delivered and when; assigns activities and artifacts to developers; offers criteria for monitoring a project s progress, for measuring the outcomes, and for planning future projects. Is not susceptible to standardization Chapter 1 (Maciaszek - RASD 3/e) 7 Iterative and incremental process An iterative process is one that involves managing a stream of executable releases. An incremental process is one that involves the continuous integration of the system s architecture to produce these releases, with each new release embodying incremental improvements over the other. (RUP) Some examples: the spiral model the Rational Unified Process (RUP) Model Driven Architecture (MDA) the agile development process aspect-oriented software development Iterative and incremental development must be planned and controlled, and must conform to a pre-defined architectural design framework (meta-architecture) Chapter 1 (Maciaszek - RASD 3/e) 8 MACIASZEK (2007): Req Analysis & Syst Design 4
5 Chapter 1 (RASD 3/e) Capability maturity model Improve process discipline Level 1 Initial Improve process definition Level 2 Repeatable Improve process control Unpredictable and undisciplined process that depends on the current staff. Level 3 Defined Improve process itself Level 4 Managed Metrics used to control the process. Both management and engineering processes are codified and followed. Repeatable project management; consistent time and effort predictions for similar projects. Level 5 Optimizing Continuous process improvement in place. Chapter 1 (Maciaszek - RASD 3/e) 9 ISO 9000 family of quality standards Developed by the International Organization for Standardization The ISO standards apply to the quality management and the process to produce a quality product apply to any industry and all types of businesses, including software development The main premise if the process is right then the process outcome (product or service) will also be right but... the ISO standards do not enforce or specify processes the standards provide models of what must be accomplished, not how activities must be performed Chapter 1 (Maciaszek - RASD 3/e) 10 MACIASZEK (2007): Req Analysis & Syst Design 5
6 Chapter 1 (RASD 3/e) ITIL framework IT as commodity Software becomes merely a service enabling business solution solution (service) delivery IT Infrastructure Library (ITIL) the most widely used and accepted framework of best practices for IT service management Efficient and effective use of the four Ps people, processes, products (tools and technology) and partners (suppliers, vendors and outsourcing organizations). Next slide - solution management as a Continuous Service Improvement Programme (CSIP) Chapter 1 (Maciaszek - RASD 3/e) 11 CSIP What is the vision? High level business objectives Where are we now? Maturity assessment How do we keep the momentum going? Where do we want to be? Measurable targets How do we get where we want to be? Process improvement plan How do we check milestones have been reached? Measurements and metrics Chapter 1 (Maciaszek - RASD 3/e) 12 MACIASZEK (2007): Req Analysis & Syst Design 6
7 Chapter 1 (RASD 3/e) COBIT framework ITIL addresses the operational side of the solution delivery and management ITIL, CMM and ISO 9000 are process standards COBIT (Control OBjectives for Information and related Technology) is a compliance framework and addresses the control side of the solution management COBIT is rather a product standard COBIT groups IT-related efforts into four domains: Plan and Organize, Acquire and Implement, Deliver and Support, and Monitor. The domains are assigned control objectives 34 high-level control objectives 318 recommended detailed control objectives Chapter 1 (Maciaszek - RASD 3/e) 13 Variable 3 - Modeling Modeling artifacts have to be communicated (language) and documented (tools) The Unified Modeling Language (UML) is a generalpurpose visual modeling language that is used to specify, visualize, construct, and document the artifacts of a software system. Computer-Assisted Software Engineering (CASE) tool enables storage and retrieval of models in a central repository and graphical and textual manipulation of models on a computer screen Chapter 1 (Maciaszek - RASD 3/e) 14 MACIASZEK (2007): Req Analysis & Syst Design 7
8 Chapter 1 (RASD 3/e) UML UML is independent of any software development process A process that adopts UML must support an object-oriented oriented approach to software production implementation technologies (as long as they are objectoriented) This makes UML somewhat deficient in supporting the detailed design phase of the development lifecycle The UML models can be categorized into three groups: State models describe the static data structures Behavior models describe object collaborations State change models describe the allowed states for the system over time Chapter 1 (Maciaszek - RASD 3/e) 15 CASE and process improvement Process improvement is much more than the introduction of new tools, methods and techniques the introduction of new methods and techniques to organization at a low level of process maturity can bring more harm than good An integrated CASE tool can allow multiple developers to collaborate and share design information in order to produce new design artifacts the tool imposes processes on the development team in immature organizations processes will not be followed (creating more mess than before) However, a CASE tool would always bring personal productivity and quality improvements to individual developers Chapter 1 (Maciaszek - RASD 3/e) 16 MACIASZEK (2007): Req Analysis & Syst Design 8
9 Chapter 1 (RASD 3/e) Development or integration? Application development Stand-alone From-scratch Integration development Value-added or Brand new application that (also) requires integration of existing apps Integration approaches Information- and/or portal-oriented Interface-oriented Process-oriented Chapter 1 (Maciaszek - RASD 3/e) 17 Review Quiz Do accidents of software development define the software development invariants? 2. What are the two main groups of stakeholders in software projects? 3. Does each incremental release within an iteration add a new functionality to the software product under development? 4. Is COBIT a product or a process standard? 5. Is portal-oriented integration a special kind of interface-oriented integration? Chapter 1 (Maciaszek - RASD 3/e) 18 MACIASZEK (2007): Req Analysis & Syst Design 9
10 Chapter 1 (RASD 3/e) 2. System planning Which IS technologies and applications will return the most value to the business? System planning System planning can be carried out in a number of different ways: SWOT Strengths, Weaknesses, Opportunities, Threats VCM Value Chain Model BPR Business Process Reengineering Information System Architecture (ISA) All system planning approaches have an important common denominator they are concerned with effectiveness rather than efficiency Chapter 1 (Maciaszek - RASD 3/e) 20 MACIASZEK (2007): Req Analysis & Syst Design 10
11 Chapter 1 (RASD 3/e) SWOT approach Mission statement Internal analysis External analysis Strengths Weaknesses Opportunities Threats SWOT matrix Objectives Goals Strategies Policies Chapter 1 (Maciaszek - RASD 3/e) 21 VCM approach The VCM (Value Chain Model) assesses competitive advantage by analyzing the full chain of activities in an organization from raw materials to final products sold and shipped to customers The question is: which value chain configurations will yield the greatest competitive advantage? The IS development projects can then target those segments, operations, distribution channels, marketing approaches, etc. that give the most competitive advantage Organizational functions are categorized into: primary activities they create or add value to a final product support activities they are essential but they do not enrich the product Chapter 1 (Maciaszek - RASD 3/e) 22 MACIASZEK (2007): Req Analysis & Syst Design 11
12 Chapter 1 (RASD 3/e) BPR approach The BPR (Business Process Reengineering) approach to system planning is based on the premise that today s organizations must reinvent themselves and abandon the functional decomposition, hierarchical structures and operational principles that they are now using Most contemporary organizations are structured in vertical units focused on functions, products or regions No one employee or department is responsible for a business process which is defined as... a collection of activities that takes one or more kinds of input and creates an output that is of value to the customer The most visible difference between a process enterprise and a traditional organization is the existence of process owners The main objective of BPR is to radically redesign business processes in an organization (hence, process redesign) The major hurdle lies in the need to embed a horizontal process in a traditional vertical management structure BPR initiative requires changing the organization around the development teams as the primary organizational units These teams are responsible for one or more end-to to-end business processes Chapter 1 (Maciaszek - RASD 3/e) 23 ISA approach ISA (Information Systems Architecture) is a bottom-up approach that offers a neutral architectural framework for IS solutions that can suit a variety of business strategies it does not include a system planning methodology it offers a framework that leverages most business strategies The ISA framework is represented as a table of thirty cells organized into five rows (labeled 1 through 5) and six columns (labeled A through F) Rows represent the different perspectives used in the construction of a complex engineering product, such as an information system five major players in the game Columns represent the six different descriptions or architectural models that each of the participants engages with Chapter 1 (Maciaszek - RASD 3/e) 24 MACIASZEK (2007): Req Analysis & Syst Design 12
13 Chapter 1 (RASD 3/e) Review Quiz What is the main target of system planning effectiveness or efficiency? 2. In the SWOT analysis, are objectives derived from goals or vice versa? 3. In the VCM approach, is sales and marketing a primary or support activity? 4. According to the BPR approach, what is the most visible difference between a process enterprise and a traditional organization? 5. What are the five perspectives of the ISA framework? Chapter 1 (Maciaszek - RASD 3/e) Systems for three management levels strategic tactical operational MACIASZEK (2007): Req Analysis & Syst Design 13
14 Chapter 1 (RASD 3/e) Systems for three management levels Level of decision making Focus of decision making Typical IS applications Typical IT solutions Pivotal concept Strategic (executive and senior management levels) Strategies in support of organizational long-term objectives Market and sales analysis, Product planning, Performance evaluation Data mining, Knowledge management Knowledge Tactical (line management level) Policies in support of shortterm goals and resource allocation Budget analysis, Salary forecasting, Inventory scheduling, Customer service Data warehouse, Analytical processing, Spreadsheets Information Operational (operative management level) Day-to-day staff activities and production support Payroll, Invoicing, Purchasing, Accounting Database, Transactional processing, Application generators Data Chapter 1 (Maciaszek - RASD 3/e) 27 Transactional processing systems OnLine Transaction Processing (OLTP) systems Transaction a logical unit of work that accomplishes a particular business task and guarantees the integrity of the database after the task completes Database technology Concurrency control Recovery Business logic (vs( application/control logic) Security Chapter 1 (Maciaszek - RASD 3/e) 28 MACIASZEK (2007): Req Analysis & Syst Design 14
15 Chapter 1 (RASD 3/e) Analytical processing systems OnLine Analytical Processing (OLAP) systems Analysis of pre-existing historical data to facilitate decision making Data warehouse technology Summarizing Packaging Partitioning Data marts Data webhouse Chapter 1 (Maciaszek - RASD 3/e) 29 Knowledge processing systems Know-how intellectual capital accumulated through experience Knowledge management to help organizations discover, organize, distribute and apply the knowledge encoded in information systems Data mining Association Classification Clustering AI techniques predictive rather than retrospective models Chapter 1 (Maciaszek - RASD 3/e) 30 MACIASZEK (2007): Req Analysis & Syst Design 15
16 Chapter 1 (RASD 3/e) Review Quiz Which level of decision making is primarily supported by the data warehouse technology? 2. What are the two main functions of transaction management in OLTP systems? 3. What kind of OLAP technology aims at supporting individual departments or business functions and stores only summarized historical data? 4. What is the main technology underpinning knowledge processing systems? Chapter 1 (Maciaszek - RASD 3/e) The software development lifecycle strategic tactical operational MACIASZEK (2007): Req Analysis & Syst Design 16
17 Chapter 1 (RASD 3/e) Software development lifecycle The lifecycle identifies: the applied modeling approach the exact phases along which the software product is transformed from initial inception to phasing it out the method (methodology) and associated development process Chapter 1 (Maciaszek - RASD 3/e) 33 Development approach Software has become much more interactive event-driven user in control software objects service random and unpredictable events Conventional software has been well served by the so-called structured approach Modern interactive GUI systems require object programming and the object approach is the best way to design such systems Chapter 1 (Maciaszek - RASD 3/e) 34 MACIASZEK (2007): Req Analysis & Syst Design 17
18 Chapter 1 (RASD 3/e) Structured approach Popularized in 1980s Based on: DFD (data flow diagrams) for process modeling ERD (entity relationship diagrams) for data modeling Process-centric Brakes system down to manageable units in the activity called functional decomposition Not well aligned with modern software engineering: sequential and transformational approach rather than iterative and incremental tends to deliver inflexible solutions that satisfy the set of identified business functions assumes development from scratch, and it does not support the reuse of pre-existing components Chapter 1 (Maciaszek - RASD 3/e) 35 Object-oriented approach Popular since 1990s Data-centric it evolves around class models But the growing significance of use cases in UML shifts the emphasis slightly from data to processes Matches the event-driven programming demanded by interactive GUI-based applications Addresses the needs of emerging applications, such as workgroup computing and multimedia systems Good at fighting application backlogs using object wrapping and similar techniques Aligns with the iterative and incremental process Chapter 1 (Maciaszek - RASD 3/e) 36 MACIASZEK (2007): Req Analysis & Syst Design 18
19 Chapter 1 (RASD 3/e) Problems related to OO development The semantic gap between the object-oriented modeling artifacts and the implementation of the data-centric artifacts with relational database technology can be significant Project management is more difficult In object-oriented development through elaboration there are no clear boundaries between phases, and project documentation evolves continuously Object solutions are significantly more complex than old-style structured systems The complexity results from the need for extensive interobject communication ( complexity in the wires ) Good architectural design a necessity Chapter 1 (Maciaszek - RASD 3/e) 37 Lifecycle phases Business Analysis functional and non-functional requirements System Design architectural design detailed design Implementation coding round-trip engineering Integration and Deployment Operation and Maintenance Chapter 1 (Maciaszek - RASD 3/e) 38 MACIASZEK (2007): Req Analysis & Syst Design 19
20 Chapter 1 (RASD 3/e) Business analysis Also requirements analysis Activity of determining and specifying customer requirements business analyst determines requirements system analyst specifies (or models) requirements Business analysis is linked to business process reengineering (BPR) aim of BPR is to propose new ways of conducting business and gaining competitive advantage Business analysis becomes increasingly an act of requirements engineering Chapter 1 (Maciaszek - RASD 3/e) 39 Requirements determination Requirement a statement of a system service or constraint Service statement a business rule that must be obeyed at all times (e.g. fortnightly salaries are paid on Wednesdays ) a computation that the system must carry out (e.g. calculate salesperson commission based on the sales in the last fortnight using a particular formula ) Constraint statement a restriction on the system s behavior ( only direct managers can see the salary information of their staff ) a restriction on the system s development ( we must use Sybase development tools ) Chapter 1 (Maciaszek - RASD 3/e) 40 MACIASZEK (2007): Req Analysis & Syst Design 20
21 Chapter 1 (RASD 3/e) Requirements specification Begins when the developers start modeling the requirements using a particular method (such as UML) CASE tool is used to enter, analyze and document the models Requirements Document is enriched with graphical models and CASE-generated reports Specifications document (the specs in the jargon) replaces the requirements document Most important specification techniques class diagrams use case diagrams Ideally, the specification models should be independent from the hardware/software platform on which the system is to be deployed Chapter 1 (Maciaszek - RASD 3/e) 41 Architectural design The description of the system in terms of its modules (components) Concerned with selection of a solution strategy to resolve client (user interface) and server (database) issues as well as any middleware needed to glue client and server processes modularization of the system relatively independent from a solution strategy but the detailed design of components must conform to a selected client/server solution Client/server models are frequently extended to provide a three-tier architecture where application logic constitutes a separate layer Good architectural design produces adaptive (supportable) systems, i.e. systems that are understandable, maintainable, and scalable (extensible) Chapter 1 (Maciaszek - RASD 3/e) 42 MACIASZEK (2007): Req Analysis & Syst Design 21
22 Chapter 1 (RASD 3/e) Detailed design Description of the internal workings of each software component Develops detailed algorithms and data structures for each component Dependent on the underlying implementation platform client server middleware Chapter 1 (Maciaszek - RASD 3/e) 43 Implementation Involves installation of purchased software coding of custom-written software other important activities, such as loading of test and production databases, testing, user training, hardware issues, etc. Client programs Server programs Chapter 1 (Maciaszek - RASD 3/e) 44 MACIASZEK (2007): Req Analysis & Syst Design 22
23 Chapter 1 (RASD 3/e) Integration and deployment Module integration can take more time and effort than any one of the earlier lifecycle phases, including implementation The whole is more than the sum of the parts (Aristotle) must be carefully planned from the very beginning of the software lifecycle Application integration integrating disparate (stovepipe) applications into a unified enterprise application through which all data and processes are shared Deployment must be carefully managed and allow, if at all possible, fallback to the old solution, if problems encountered Chapter 1 (Maciaszek - RASD 3/e) 45 Operation and maintenance Operation signifies change over from the existing business solution, whether in software or not Maintenance is not only an inherent part of the software lifecycle it accounts for most of it as far as IT personnel time and effort is concerned Housekeeping Adaptive maintenance Perfective maintenance Phasing out would normally happen due to reasons that have little to do with the usefulness of the software Chapter 1 (Maciaszek - RASD 3/e) 46 MACIASZEK (2007): Req Analysis & Syst Design 23
24 Chapter 1 (RASD 3/e) Activities spanning the lifecycle Project planning Metrics Testing Chapter 1 (Maciaszek - RASD 3/e) 47 Project planning If you can t plan it, you can t do it Activity of estimating the project s deliverables, costs, time, risks, milestones, and resource requirements Includes the selection of development methods, processes, tools, standards, team organization, etc. A moving target Typical constraints are time and money Chapter 1 (Maciaszek - RASD 3/e) 48 MACIASZEK (2007): Req Analysis & Syst Design 24
25 Chapter 1 (RASD 3/e) Metrics Measuring development time and effort Without measuring the past, the organization is not able to plan accurately for the future Metrics are usually discussed in the context of software quality and complexity they apply to the quality and complexity of the software product Equally important application of metrics is measuring the development models (development products) at different phases of the lifecycle to assess the effectiveness of the process and to improve the quality of work at various lifecycle phases Chapter 1 (Maciaszek - RASD 3/e) 49 Testing Test cases should be defined for each functional module (use case) described in the requirements document Desktop testing by developers not sufficient Methodical testing by Software Quality Assurance (SQA) group necessary Requirements, specifications and any documents (including program source code) can be tested in formal reviews (so-called walkthroughs and inspections) Execution-based testing: Testing to specs (black-box testing) Testing to code (white-box or glass-box testing) Chapter 1 (Maciaszek - RASD 3/e) 50 MACIASZEK (2007): Req Analysis & Syst Design 25
26 Chapter 1 (RASD 3/e) Review Quiz Which software development approach, structured or object-oriented, takes advantage of the activity of functional decomposition? 2. What is another name for business analysis? 3. Which development phase is largely responsible for producing/delivering an adaptive system? 4. The notion of a stub is associated with what development phase? 5. Which activities span the development lifecycle and are not, therefore, distinct lifecycle phases? Chapter 1 (Maciaszek - RASD 3/e) Development models and methods how of software production called also lifecycle models MACIASZEK (2007): Req Analysis & Syst Design 26
27 Chapter 1 (RASD 3/e) Development models Model defines an approach to software production Has an associated process iterative and incremental Process is unique (different) for each organization Representative models for iterative and incremental development: the spiral model the IBM Rational Unified Process (RUP) Model Driven Architecture (MDA) agile software development aspect-oriented development Chapter 1 (Maciaszek - RASD 3/e) 53 Spiral model Project cost Planning Risk analysis go, no-go decision Project progress Customer evaluation Engineering Chapter 1 (Maciaszek - RASD 3/e) 54 MACIASZEK (2007): Req Analysis & Syst Design 27
28 Chapter 1 (RASD 3/e) IBM Rational Unified Process (RUP) Requirements Analysis & Design Business Modeling Management Environment Configuration Management Deployment Start of the process Implementation Test RUP organizes projects in twodimensional terms The horizontal dimension represents the successive phases of each project iteration: inception, elaboration, construction, and transition. The vertical dimension represents seven software development disciplines and supporting activities of configuration and change management, project management, and environment. Chapter 1 (Maciaszek - RASD 3/e) 55 Model Driven Architecture (MDA) Customer requirements Mostly text Analysis Platform Independent Model Design Coding Applicable standards: Unified Modeling Language (UML) Meta-Object Facility (MOF) for using a Platform Specific Model Code PSM bridge Code bridge Platform Specific Model Code standard meta-model repository so that derived specifications can work together XML Meta-Data Interchange (XMI) for mapping UML to XML for interchange purposes, Common Warehouse Meta-model (CWM) for mapping of MDA to database schemas and permitting flexible data mining. Chapter 1 (Maciaszek - RASD 3/e) 56 MACIASZEK (2007): Req Analysis & Syst Design 28
29 Chapter 1 (RASD 3/e) Agile software development Key points of agility in software production: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan The best known representatives: extreme Programming (XP) Aspect Oriented Software Development Feature-Driven Development Lean Development Acceptance tests Test-driven development User stories Refactoring Continuous integration Chapter 1 (Maciaszek - RASD 3/e) 57 Aspect-oriented software development Produces more modular systems by identifying so called crosscutting concerns Typically, nonfunctional requirements/qualities The modules are called aspects Base code vs aspect code The aspects are integrated through the process called aspect weaving Static vs dynamic weaving Applies to join points in a program s execution A particular action that needs to be taken for a join point is called an advice Aspects Aspect weaving Crosscutting concerns Join points Advice Chapter 1 (Maciaszek - RASD 3/e) 58 MACIASZEK (2007): Req Analysis & Syst Design 29
30 Chapter 1 (RASD 3/e) Review Quiz Is adding a new functionality to a software project the responsibility of a software iteration or integration? 2. Which of the development models/methods is most explicit about risk analysis? 3. Which development model/method is directly linked to the traditional concept of formal specifications? 4. Which development model/method is directly linked to the concept of intentional programming? 5. Which development model/method is directly linked to the concept of crosscutting concerns? Chapter 1 (Maciaszek - RASD 3/e) 59 Case studies (separate set of slides) University Enrolment (UE) Video Store (VS) Contact Management (CM) Telemarketing (TM) Advertising Expenditure (AE) Time Logging (TL) Currency Converter (CC) Chapter 1 (Maciaszek - RASD 3/e) 60 MACIASZEK (2007): Req Analysis & Syst Design 30
31 Chapter 1 (RASD 3/e) Summary The nature of software development is that of a craft or even art. The triangle for success includes the stakeholders factor, a sound process and the support of a modeling language and tools. System planning precedes software development and determines which products can be most effective to the organization. Modern software products are object-oriented. Software development follows a lifecycle. Modern development lifecycles and processes are iterative and incremental. Chapter 1 (Maciaszek - RASD 3/e) 61 MACIASZEK (2007): Req Analysis & Syst Design 31
Chapter 1 Software Process
MACIASZEK, L.A. (2005): Requirements Analysis and System Design, 2 nd ed. Addison Wesley, Harlow England, 504p. ISBN 0 321 20464 6 Chapter 1 Software Process Pearson Education Limited 2005 Topics The nature
More information(c) Addison Wesley Chapter 1. ! Software production is an art. ! Two groups. ! Main causes of software failures
MACIASZEK, L.A. (2001): Requirements Analysis and System Design. Developing Information Systems with UML, Addison Wesley Chapter 1 Software Process Copyright 2000 by Addison Wesley Version 1.0 Software
More informationCredit where Credit is Due. Lecture 2: Software Engineering (a review) Goals for this Lecture. What is Software Engineering
Credit where Credit is Due Lecture 2: Software Engineering (a review) Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 6448 - Spring Semester, 2002 Some material presented in this lecture is
More informationRational Unified Process (RUP) in e-business Development
Rational Unified Process (RUP) in e-business Development Jouko Poutanen/11.3.2005 2004 IBM Corporation Agenda Characteristics of e-business Development Business Modeling with RUP and UML Rational Tools
More informationSistemi ICT per il Business Networking
Corso di Laurea Specialistica Ingegneria Gestionale Sistemi ICT per il Business Networking Requirements Engineering Docente: Vito Morreale (vito.morreale@eng.it) 17 October 2006 1 UP Phases 1. Inception
More informationThe Art of Agile Practice
The Art of Agile Practice A Composite Approach for Projects and Organizations Bhuvan Unhelkar Lap) CRC Press VV^ ^^-""^ J Taylor & Francis Group Boca Raton London New York CRC Press is an imprint of the
More informationSoftware Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationLecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
More information7. Model based software architecture
UNIT - III Model based software architectures: A Management perspective and technical perspective. Work Flows of the process: Software process workflows, Iteration workflows. Check Points of The process
More informationEnterprise Architecture Development
Methodology Overview Prepared For: Our Valued Clients Introduction Page 2 Engagement Objectives Perform an assessment of the current Enterprise against the short and long term IT and Business Strategic
More information5) A work breakdown structure is a list of tasks broken down to small manageable activities. Answer: TRUE Diff: 2 Page Ref: 42
Project Management: Process, Technology, and Practice (Vaidyanathan) Chapter 2 Process and Methods 2.1 True False 1) A procedure defines how to do a task. Diff: 1 Page Ref: 38 2) A business process is
More informationSoftware Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationChapter 1 Systems Development in an Organization Context
Systems Development in an Organization Context Learning Objectives Define information systems analysis and design. Describe the information Systems Development Life Cycle (SDLC). Explain Rapid Application
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Building Skills is a 3-day course that is a subset of our course. The course is designed to provide a fundamental knowledge base and practical skills for anyone interested in implementing or improving
More informationRational Software White Paper TP 174
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP 174 Table of Contents Abstract... 1 Introduction... 1 Level 2, Repeatable... 2 Requirements Management...
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Courses is a 2-day course that is a subset of our course. The course is designed to provide an overview of techniques and practices. This course starts with an overview of software quality engineering
More informationSystems Analysis and Design 8 th Edition. Chapter 1 Introduction to Systems Analysis and Design
Systems Analysis and Design 8 th Edition Chapter 1 Introduction to Systems Analysis and Design Chapter Objectives Discuss the impact of information technology on business strategy and success Define an
More informationObjectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationTopics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationSoftware Engineering
Software Engineering (CS550) Software Development Process Jongmoon Baik Software Development Processes (Lifecycle Models) 2 What is a S/W Life Cycle? The series of stages in form and functional activity
More informationModern Systems Analysis and Design Seventh Edition
Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich The Systems Development Environment Learning Objectives Define information systems analysis and design.
More informationChapter. Redesigning The Organization With Information Systems
Chapter Redesigning The Organization With Information Systems 1 Objectives Demonstrate how building new systems produces organizational change Explain how a company can develop information systems that
More informationPassit4Sure.OG Questions. TOGAF 9 Combined Part 1 and Part 2
Passit4Sure.OG0-093.221Questions Number: OG0-093 Passing Score: 800 Time Limit: 120 min File Version: 7.1 TOGAF 9 Combined Part 1 and Part 2 One of the great thing about pass4sure is that is saves our
More informationIn Pursuit of Agility -
In Pursuit of Agility - BPM and SOA within the Boeing Company Ahmad R. Yaghoobi Associate Technical Fellow Enterprise Architect ahmad.r.yaghoobi@boeing.com Randy Worsech Business Architect Randall.a.worsech@boeing.com
More informationCHAPTER 1. Business Process Management & Information Technology
CHAPTER 1 Business Process Management & Information Technology Q. Process From System Engineering Perspective From Business Perspective In system Engineering Arena Process is defined as - a sequence of
More informationThe software process
Software Processes The software process A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. A software process model is an abstract representation
More informationTOGAF 9.1 Phases E-H & Requirements Management
TOGAF 9.1 Phases E-H & Requirements Management By: Samuel Mandebvu Sources: 1. Primary Slide Deck => Slide share @ https://www.slideshare.net/sammydhi01/learn-togaf-91-in-100-slides 1. D Truex s slide
More informationIntroduction. Figure 1-1
Chapter Objectives Discuss the impact of information technology on business strategy and success Define an information system and describe its components Explain how profiles and models can represent business
More informationTranslate stakeholder needs into strategy. Governance is about negotiating and deciding amongst different stakeholders value interests.
Principles Principle 1 - Meeting stakeholder needs The governing body is ultimately responsible for setting the direction of the organisation and needs to account to stakeholders specifically owners or
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2008 Vol. 7, No. 1, January-February 2008 The Year of the Globally Integrated Enterprise Mahesh
More informationFederal Segment Architecture Methodology Overview
Federal Segment Architecture Methodology Background In January 2008, the Federal Segment Architecture Working Group (FSAWG) was formed as a sub-team of the Federal CIO Council s Architecture and Infrastructure
More informationCourse Organization. Lecture 1/Part 1
Course Organization Lecture 1/Part 1 1 Outline About me About the course Lectures Seminars Evaluation Literature 2 About me: Ing. RNDr. Barbora Bühnová, Ph.D. Industrial experience Research Quality of
More informationCORE APPLICATIONS ANALYSIS OF BUSINESS-CRITICAL ADABAS & NATURAL
ADABAS & NATURAL ANALYSIS OF BUSINESS-CRITICAL CORE APPLICATIONS CONTENTS 2 Core applications in a changing IT landscape 3 The need for comprehensive analysis 4 The complexity of core applications 5 An
More informationIntroduction of RUP - The Rational Unified Process
Introduction of RUP - The Rational Unified Process Jong-Hoon Lee Dependable Software Laboratory Konkuk University References Textbook: The Rational Unified Process Made Easy A Practitioner s Guide to the
More informationRedesigning the Organization with Information Systems
Chapter 14 Redesigning the Organization with Information Systems 14.1 2006 by Prentice Hall OBJECTIVES Demonstrate how building new systems produces organizational change Explain how a company can develop
More informationCLASS/YEAR: II MCA SUB.CODE&NAME: MC7303, SOFTWARE ENGINEERING. 1. Define Software Engineering. Software Engineering: 2. What is a process Framework? Process Framework: UNIT-I 2MARKS QUESTIONS AND ANSWERS
More informationMDA Overview Applied MDA
IBM Software Group MDA Overview Applied MDA Jim Amsden Senior Software Engineer IBM Rational Software jamsden@us.ibm,com Tutorial: MDA, UML, and applicability to SOA (C) IBM Corporation March 2006 Agenda!
More informationCompetency Area: Business Continuity and Information Assurance
Competency Area: Business Continuity and Information Assurance Area Description: Business Continuity and Information Assurance competency area mainly concerns the continuity, auditing and assurance of
More informationCONTENTS. Part I BUSINESS PROCESSES AND INFORMATION SYSTEMS FOUNDATION 1. Part II TECHNOLOGY FOR BUSINESS PROCESSES AND INFORMATION SYSTEMS 65
CONTENTS Part I BUSINESS PROCESSES AND INFORMATION SYSTEMS FOUNDATION 1 Chapter 1 Introduction to Information Systems 2 Synopsis 3 Introduction 4 The Textbook s Three Themes 4 Challenges and Opportunities
More informationProcesses. Object Orientated Analysis and Design. Benjamin Kenwright
Processes Object Orientated Analysis and Design Benjamin Kenwright Outline Review What are Processes? Why are they important in Object Orientated Analysis and Design Conclusion and Discussion Summary Revision
More informationThe information contained herein is subject to change without notice.
The information contained herein is subject to change without notice. This is a QAI Copyrighted work which may not be reproduced without the written permission of QAI. You may not use these materials to
More informationChapter 1. What is Software Engineering. Shari L. Pfleeger Joanne M. Atlee. 4 th Edition
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition Contents 1.1 What is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does
More informationChapter 3. Information Systems Development. McGraw-Hill/Irwin. Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 3 Information Systems Development McGraw-Hill/Irwin Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Objectives 3-2 Describe the motivation for a system development process
More informationUnifying Systems and Software Teams: A Holistic Approach to Systems Development
May 2004 Unifying Systems and Software Teams: A Holistic Approach to Systems Development Dave West Group Manager IBM Rational Software Robert A. Maksimchuk Industrial Solutions Market Manager IBM Rational
More informationTOGAF usage in outsourcing of software development
Acta Informatica Pragensia 2(2), 2013, 68 76, ISSN 1805-4951 Section: Online: aip.vse.cz Peer-reviewed papers TOGAF usage in outsourcing of software development Aziz Ahmad Rais 1, Rudolf Pecinovsky 1 1
More informationChapter 4 The Implementation Methodology Chapter Overview
Chapter 4 The Implementation Methodology Chapter Overview This chapter describes the EA implementation methodology (EA methodology), which is a detailed procedure for establishing, maintaining and using
More information1 Accounting Information Systems Revision
1 IS and AIS Concepts - Defining accounting information system (AIS) is difficult as: o AIS needs to carve out a field of its own distinct of other disciplines o The landscape is constantly evolving and
More informationExam Questions OG0-091
Exam Questions OG0-091 TOGAF 9 Part 1 https://www.2passeasy.com/dumps/og0-091/ 1. According to TOGAF, Which of the following are the architecture domains that are commonly accepted subsets of an overall
More informationTOGAF 9 Training: Foundation
TOGAF 9 Training: Foundation Part I: Basic Concepts Document version control information Document Name Document Status Document Owner Part I: Basic Concepts Final IT Management Group TOGAF Lead Trainer
More informationSoftware Development Methodologies. CSC 440: Software Engineering Slide #1
Software Development Methodologies CSC 440: Software Engineering Slide #1 Topics 1. The Waterfall Model 2. Agile Software Development 3. The Unified Process 4. Object-Oriented Analysis and Design 5. The
More informationGuide to Modernize Your Enterprise Data Warehouse How to Migrate to a Hadoop-based Big Data Lake
White Paper Guide to Modernize Your Enterprise Data Warehouse How to Migrate to a Hadoop-based Big Data Lake Motivation for Modernization It is now a well-documented realization among Fortune 500 companies
More informationData Warehousing provides easy access
Data Warehouse Process Data Warehousing provides easy access to the right data at the right time to the right users so that the right business decisions can be made. The Data Warehouse Process is a prescription
More information2013 Rational Software Open Labs
2013 Rational Software Open Labs Target to better LEARNING (not substitution for full training course) Software Choose from one or more of twelve Self-Paced, Hands-On Labs: Rational System Architect for
More informationHow SOA Can Help EA. Enterprise Architecture Conference 2008
Enterprise Conference 2008 The IT & Business Alignment Forum November 10-13, 2008, Las Vegas, NV How SOA Can Help EA Yan Zhao, Ph.D Enterprise and IT Strategy Current Affiliation: Mitre Corporation Presentation
More informationObject-Oriented Software Engineering
Object-Oriented Software Engineering Using UML, Patterns, and Java Software Lifecycle Modeling: Reengineering Object-Oriented Software Engineering Using UML, Patterns, and Java Software Lifecycle Models
More informationProcess, Models, Methods, Diagrams Software Development Life Cyles. Part - II
Process, Models, Methods, Diagrams Software Development Life Cyles Part - II A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process maturity based
More informationChapter 1. Contents. What is Software Engineering 9/9/13. Shari L. Pfleeger Joanne M. Atlee. 4 th Edition
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition Contents 1.1 What is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does
More informationCHAPTER 3 ENTERPRISE SYSTEMS ARCHITECTURE
CHAPTER 3 ENTERPRISE SYSTEMS ARCHITECTURE 1 Learning Objectives Examine in detail the enterprise systems modules and architecture. Understand the effects of a well-designed architecture on ERP implementation.
More informationHarry J. Rosenblatt. (2014). Systems Analysis and Design, 10 th Edition, International Edition. Course Technology, Cengage Learning.
Chapter 1 Introduction to Systems Analysis and Design Harry J. Rosenblatt. (2014). Systems Analysis and Design, 10 th Edition, International Edition. Course Technology, Cengage Learning. Describe the impact
More informationThe Systems Development Lifecycle
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system developments projects The project Major attributes of the Lifecycle Moves systematically
More informationMANAGEMENT INFORMATION SYSTEMS COURSES Student Learning Outcomes 1
MANAGEMENT INFORMATION SYSTEMS COURSES Student Learning Outcomes 1 MIS 180: Principles of Information Systems 1. Explain the importance of determining information system requirements for all management
More informationQUALITY ASSURANCE PLAN OKLAHOMA DEPARTMENT OF HUMAN SERVICES ENTERPRISE SYSTEM (MOSAIC PROJECT)
QUALITY ASSURANCE PLAN OKLAHOMA DEPARTMENT OF HUMAN SERVICES ENTERPRISE SYSTEM (MOSAIC PROJECT) MOSAIC Quality Assurance Plan v04.02 Prepared by: Approved by: QUALITY ASSURANCE PLAN APPROVALS QA/QC Program
More informationSucceed with Agile at Scale
IBM Software Group Succeed with Agile at Scale Alfred Tse/Osmond Ng Rational Software Technical Professionals Growth Markets Asia Pacific June 25, 2009 2008 IBM Corporation Agenda Agile Software Development
More informationCSE 435 Software Engineering. Sept 14, 2015
CSE 435 Software Engineering Sept 14, 2015 What is Software Engineering Where Does the Software Engineer Fit In? Computer science: focusing on computer hardware, compilers, operating systems, and programming
More informationTOGAF Foundation Exam
TOGAF Foundation Exam TOGAF 9 Part 1 (ESL) Time Limit 90 minutes Number of questions 40 Pass-through 22 1. Which of the following best describes the meaning of "Initial Level of Risk" in Risk Management?
More informationAUTOMATED DEFECT PREVENTION: BEST PRACTICES IN SOFTWARE MANAGEMENT
AUTOMATED DEFECT PREVENTION: BEST PRACTICES IN SOFTWARE MANAGEMENT Preface. Features and Organization. Practice Descriptions. Intended audience. Acknowledgements. Permissions. Disclaimer. 1. The Case for
More informationContents An Introductory Overview of ITIL Service Lifecycle: concept and overview...3 I. Service strategy...6 The 4 P's of ITIL Service
ITIL 2011 Notes Contents An Introductory Overview of ITIL 2011...3 Service Lifecycle: concept and overview...3 I. Service strategy...6 II. The 4 P's of ITIL Service Strategy...6 Key processes and activities...7
More informationRequirements Analysis and Design Definition. Chapter Study Group Learning Materials
Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this
More informationKatherine Marshak. Professional Summary. Technical Skills
Professional Summary Over eleven years experience performing complete software engineering lifecycle activities for insurance, logistics, and management information systems. This includes planning, requirements
More informationMDA Legacy Modernization Case Study: State of Wisconsin Unemployment Insurance Division
MDA Legacy Modernization Case Study: State of Wisconsin Unemployment Insurance Division ADM Workshop 2004 Adaptive Team Collaboration, Inc. 7402 Borman Avenue St. Paul, MN 55076 651.554.1771 www.atcprocess.com
More informationChapter 3 Prescriptive Process Models
Chapter 3 Prescriptive Process Models - Generic process framework (revisited) - Traditional process models - Specialized process models - The unified process Generic Process Framework Communication Involves
More informationSoftware Engineering in the Agile World. Table of contents
Table of contents Chapter 1 14 Software Engineering 14 1.1 Introduction 14 1.2 No standard software engineering methodology 14 1.3 Waterfall methodology 15 1.3.1 Software development under Waterfall model
More informationChapter 1. Contents. 1.1 What is Software Engineering! Solving Problems. Objectives. What is Software Engineering
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition Contents 1.1 What is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does
More informationDEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers UNIT 1 1. What are software myths Answer: Management myths: We already have a book
More informationQuality 24 Process Improvement 26 Real processes. Product Quality. Quality Management. Quality Management. Quality Plan
Quality 24 Process Improvement 26 Real processes Cleanroom RUP XP Software Engineering 55 Software Engineering 56 Product Quality Acceptable: usable, learnable, compatible Efficient: response time, memory
More informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More informationTOGAF Foundation. Part I: Basic Concepts 1 /
TOGAF Foundation Part I: Basic Concepts 1 / Enterprise and Enterprise Architecture An Enterprise is any collection of organizations that has a common set of goals, for example: Government agency Whole
More informationNote 10: Software Process
Computer Science and Software Engineering University of Wisconsin - Platteville Note 10: Software Process Yan Shi Lecture Notes for SE 3330 UW-Platteville Based on Pressman Chapter 2 & 3 Software Process
More informationIN the inaugural issue of the IEEE Transactions on Services Computing (TSC), I used SOA, service-oriented consulting
IEEE TRANSACTIONS ON SERVICES COMPUTING, VOL. 1, NO. 2, APRIL-JUNE 2008 62 EIC Editorial: Introduction to the Body of Knowledge Areas of Services Computing Liang-Jie (LJ) Zhang, Senior Member, IEEE IN
More informationCIM Forum Charter Dated
CIM Forum Charter Dated 2018-12-18 The information provided below is subject to change and reflects the current state of the CIM Forum charter within the DMTF. Management Problem(s) and Environment The
More informationThe IBM Rational Software Development Platform
IBM Software Group The IBM Rational Software Development Platform An overview Marc Haeverans marc.haeverans@be.ibm.com 2006 IBM Corporation Agenda The Challenge Software Development and SOA Rational Software
More informationSYLLABUS. What is Agility, What is an Agile Process, Agile Process Models.
Contents i SYLLABUS UNIT - I CHAPTER - 1 : INTRODUCTION TO Introduction to Software Engineering. CHAPTER - 2 : A GENERIC VIEW OF PROCESS Software Engineering, Process Framework, CMMI, Process Patterns,
More informationGLOBAL CENTRE OF EXCELLENCE (GCE) EXCEL AND LEAD
Internationally Accredited Certifications Leader in the Professional Training and Certification Industry GLOBAL CENTRE OF EXCELLENCE (GCE) EXCEL AND LEAD Website: www.gcenet.com Email: info@gcenet.com
More informationChapter 14 Current trends in system development
Chapter 14 Current trends in system development Dr. Supakit Nootyaskool Faculty of Information Technology King Mongkut s Institute of Technology Ladkrabang Outline Trends in System Development Methodologies
More informationBy: Ronny Trefftzs CSCI 5828: Foundations of Software Engineering Spring 2012 Professor: Kenneth Anderson
By: Ronny Trefftzs CSCI 5828: Foundations of Software Engineering Spring 2012 Professor: Kenneth Anderson WATERFALL? XP? SCRUM? While there is really no standard solution, the following presentation will
More informationImplementing Enterprise Architecture with MDA
Implementing Enterprise with MDA Mike Rosen CTO, M²VP Mrosen@m2vp.com Copyright M 2 VP Inc. 2003, All rights reserved Agenda What is Enterprise? What does it mean to implement it? How does MDA help? Enterprise
More informationEVALUATION OF ARIS AND ZACHMAN FRAMEWORKS AS ENTERPRISE ARCHITECTURES
UDC: 004.45 Original scientific paper EVALUATION OF ARIS AND ZACHMAN FRAMEWORKS AS ENTERPRISE ARCHITECTURES Melita Kozina University of Zagreb,Faculty of Organization and Informatics, Varaždin, Croatia
More informationToolbox for Architecture Framework Discussions at The Open Group. SKF Group, February 2018
Toolbox for Architecture Framework Discussions at The Open Group SKF Group, February 2018 Toolbox Overview Components in our Enterprise Architecture Management: APPROACH FRAMEWORK CONTENT TOOLBOX Architecture
More informationArchiMate Examples Eero Hosiaisluoma By Eero Hosiaisluoma. Snapshot from the blog ( )
ArchiMate Examples By Eero Hosiaisluoma Snapshot from the blog (2018-09-01) http://www.hosiaisluoma.fi/blog/ 1 Table of Contents 1. Introduction... 3 2. ArchiMate Example Views... 4 Framework View... 4
More informationAn Overview of Software Process
An Overview of Software Process Objectives To introduce the general phases of the software development life cycle (SDLC) To describe various generic software process models and discuss their pros and cons
More informationThe Rational Unified Process for Systems Engineering PART II: Distinctive Features
The Rational Unified Process for Systems Engineering PART II: Distinctive Features by Murray Cantor Principal Consultant Rational Software Corporation In Part I of this article, published in last month's
More informationSoftware Engineering Part 2
CS 0901341 Software Engineering Part 2 In this part, we look at 2.1 Software Process 2.2 Software Process Models 2.3 Tools and Techniques for Processing Modelling As we saw in the previous part, the concept
More informationReporting for Advancement
Strategies for Supporting Advancement and Development Reporting for Advancement The Changing Economics of Business Intelligence The changing economics of business intelligence make this technology feasible
More informationAGILE DEVELOPMENT AND ITS IMPACT ON PRODUCTIVITY
AGILE DEVELOPMENT AND ITS IMPACT ON PRODUCTIVITY 2006 International Software Measurement & Analysis Conference David Garmus www.davidconsultinggroup.com Topics Characteristics of Agile Projects Performance
More informationWhat are requirements? Basics of Requirement Engineering. Definition of a Stakeholder. Stated Vs. Real Requirements. Stated Vs.
What are requirements? Basics of Requirement Engineering Muzaffar Iqbal Farooqi A requirement is a necessary attribute in a system, a statement that identifies a capability, characteristic, or quality
More informationSuccessfully Selecting Object-Oriented A&D Tools
Decision Framework, J. Duggan Research Note 26 September 2002 Successfully Selecting Object-Oriented A&D Tools Gaps in object-oriented analysis and design tool functionality inhibit reliable and predictable
More informationIntroduction to Software Engineering
UNIT I SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, objects oriented) -system engineering computer
More informationDeveloped by: Steven Jacobs, Eck Doerry
Developed by: Steven Jacobs, Eck Doerry 1 Consequences of Bad Requirements Engineering http://www.knovelblogs.com/2012/08/30/the-importance-of-requirements-engineering/ 2 Building an efficient organization
More informationFrameworx 11 Certification Report Business Process Framework Release 9.0
Frameworx 11 Certification Report Business Process Framework Release 9.0 cvidya MoneyMap Release 6.5 October 2011 TM Forum 2011 Table of Contents Table of Contents... 2 List of Tables... 3 List of Figures...
More informationTOGAF 9.1 in Pictures
TOGAF 9. in Pictures The TOGAF ADM Cycle Stage Set up an EA team and make sure it can do its work The ADM is about understanding existing architectures and working out the best way to change and improve
More information