Software Acquisition and Project Management Lesson I: Introduction.

Slides:



Advertisements
Similar presentations
Chapter 3: Software Basics Section I: Preparing to Use Technology.
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
NML/436/L1-1 Nazareth Northwestern Mutual Life Participants in IS Development l A team of people comprising: l Project Manager l Systems Analysts l Specialists.
Software Quality Assurance Plan
NEES Project Management Workshop June 16 June 18 1 Segment 2.
1 SYS366 Week 1 - Lecture 2 How Businesses Work. 2 Today How Businesses Work What is a System Types of Systems The Role of the Systems Analyst The Programmer/Analyst.
Introduction to Software Architecture. What is Software Architecture?  It is the body of methods and techniques that help us to manage the complexities.
IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer 2003.
IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer Fall 2004.
1 IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer Fall 2005.
SE 555 – Software Requirements & Specifications Introduction
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
1 Objective of today’s lesson S oftware engineering occurs as a consequence of a process called system engineering. Instead of concentrating solely on.
Project Management Body of Knowledge PMBOK
Requirements Engineering
Software Product Lines Krishna Anusha, Eturi. Introduction: A software product line is a set of software systems developed by a company that share a common.
Chapter 17 Acquiring and Implementing Accounting Information Systems
Computer Software.
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
COMPUTER SOFTWARE ALISA RAHMANI PUTRI / VIDIYA RACHMAWATI /
© M. Eisenberg 2010 Approach to Information Problem-Solving Introducing.
CPTE 209 Software Engineering Summary and Review.
Chapter 2 Introduction to Requirements Management
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
CSI315 Web Applications and Technology Overview of Systems Development (342)
1 Phases in Software Development Lecture Software Development Lifecycle Let us review the main steps –Problem Definition –Feasibility Study –Analysis.
Calculation BIM Curriculum 07. Topics  Calculation with BIM  List Types  Output.
Information Technology
Software System Engineering: A tutorial
System Development Process Prof. Sujata Rao. 2Overview Systems development life cycle (SDLC) – Provides overall framework for managing system development.
OHT 23.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The benefits of use of standards The organizations involved in standards.
Foundations of Geospatial System Development Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute The.
Introduction PMBOK® © Whizlabs.
2 Systems Architecture, Fifth Edition Chapter Goals Describe the activities of information systems professionals Describe the technical knowledge of computer.
Feasibility Study.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Introduction To System Analysis and Design
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
© 2001 Business & Information Systems 2/e1 Chapter 8 Personal Productivity and Problem Solving.
Lead Black Slide Powered by DeSiaMore1. 2 Chapter 8 Personal Productivity and Problem Solving.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
Lecture 7: Requirements Engineering
1 Introduction to Software Engineering Lecture 1.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Software Project Management. Contents Project Management  Metrics for Process and Projects  Estimation  Project Scheduling  Risk Management  Quality.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
1 Chapter 1 Introduction to Databases Transparencies.
FOUNDATION IN INFORMATION TECHNOLOGY (CS-T-101) TOPIC : INFORMATION SYSTEM – SOFTWARE.
Foundations of Geospatial System Development Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute The.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CEN 4021 Software Engineering II Instructor: Peter Clarke Spring 2005.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
1 Multimedia Development Team. 2 To discuss phases of MM production team members Multimedia I.
1 Statements of Work – Getting Them Right!!. 2 Today’s Agenda A.The Basics B. Sources of Information C. Scenario #1: Procurement is in the loop D. Scenario.
Identify internal hardware devices (e. g
Chapter 1 Computer Technology: Your Need to Know
Software Engineering (CSI 321)
Quality management standards
Introduction to Software Testing
Chapter 1 (pages 4-9); Overview of SDLC
Requirements Engineering Introduction
Software Engineering Furqan Rustam.
Introduction to Requirements Management
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Software Engineering Lecture #3
System architecture, Def.
Presentation transcript:

Software Acquisition and Project Management Lesson I: Introduction

Getting to know Me? * criteria…  Name/nickname  Degree  What are your likes/dislikes?  Technology  Life  What do you expect from the instructor?  What do you expect to learn?  What grade you want to achieve?  After your bachelor’s degree, what is your next plan?

Course Description  This course provides a high level introduction to two areas that are crucial to the IT profession, namely software acquisition and project management.  It introduces students to the phases both in the project management and software acquisition and implementation process.  Since requirements are crucial to both activities, the course will provide students with an in-depth introduction to requirements engineering.  The course will also introduce students to a widely used project management information system.

Software Acquisition  Computer Software determines the types of tasks a computer can help you to accomplish. These are the computer programs and any additional files that are provided to carry out a specific type of task.  Program is a set of instructions that a computer follows in order to perform a specific function.  Software programs written used to control and direct hardware functions and operations. Categories of Software 1. Application or Custom or Private software 2. General-purpose software 3. Systems software 4. Rogue software

1. Application or Custom or Private Software  It is the software designed and written to perform a specific task for computer users.  It adapts the computer to the task the user wants done.  Examples:  Payroll System Video Rental  Database System Registration  and Billing System Grocery  Inventory System Library Database System 2. General-purpose Software  It is the software that provides the framework for a great number of business and personal applications.  Most general-purpose software is sold as a package(sold with manuals).  Examples:  Word Processing Software  Spreadsheet Software  Presentation Graphics Software  Multimedia Software  Desktop Publishing Software  Database Management System (DBMS)  Utility Software  Web Authoring Software  Number Crunching Software

3. Systems Software  The system software controls the operation of a computer and its devices, as well as enables application software to run on the PC.  The operating system is the main component of system software that enables the computer to manage its activities and the resources under its control, run application programs, and interface with the user.  It is software designed to help control the computer system.  It is independent of any specific applications area. TYPES OF SYSTEMS SOFTWARE 1. Operating Systems 2. Programming Languages 3. Translators 4. Rogue software  Any software that runs on the computer without the user’s knowledge and consents that does damage to computer files.  TYPES OF ROGUE SOFTWARE 1. Back Doors 2. Chameleon 3. Logic Bombs 4. Trojan Horses 5. ANSI Bombs 6. Worm 7. Virus

Software Acquisition  Acquisition is the process of obtaining products and services through contracting.  Those organizations that are purchasing or commissioning, rather than developing, at least some of the products or parts of the products.  The growing trend towards outsourcing or off shoring makes this practice area much more common.

Software Acquisition  Software Acquisition is where requirements engineering significantly meets business strategy.  For many organizations, software development is not an option.  Cost, skills, and the availability of software solutions on the market mean that acquisition is always the chosen route and requirements engineering is always done in this context.

Software Engineering Practice Areas Software engineering practice areas are those necessary for applying the appropriate technology to create and evolve both core assets and products. They are:  Architecture Definition  Architecture Evaluation  Component Development  Mining Existing Assets  Requirements Engineering Requirements Engineering  Software System Integration  Testing  Understanding Relevant Domains  Using Externally Available Software

Requirements Engineering  Requirements are statements of what the system must do, how it must behave, the properties it must exhibit, the qualities it must possess, and the constraints that the system and its development must satisfy.  The Institute of Electrical and Electronics Engineers (IEEE) defines a requirement as  A condition or capability needed by a user to solve a problem or achieve an objective  A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document  A documented representation of a condition or capability as definition 1 & 2

Project Management  Project Management is the art of matching a project’s goals, tasks and resources to accomplish a goal as needed.  Is the discipline of carefully projecting or planning, organizing, motivating and controlling resources to achieve specific goals and meet specific success criteria.  Is a methodical approach to planning and guiding project processes from start to finish.

Related Topics:  Project Management Methodology  Project Scope and Activity-planning  Planning, estimation and scheduling  Team Management  Project Monitoring and control