Prepared by : Dinesh Bajracharya Nepal Information System Development.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

DBS Development Lifecycle & DB Analysis
Database Planning, Design, and Administration
System Development Life Cycle (SDLC)
Presentation by Prabhjot Singh
Chapter 2 – Software Processes
Database Development Cycle Track 3: Managing Information Using Database.
Chapter 8 Information Systems Development & Acquisition
The Architecture Design Process
Chapter 6 Database Design
Software Engineering Incorporating Interface Design Into Software Engineering.
Ch7: Software Production Process. 1 Questions  What is the life cycle of a software product?  Why do we need software process models?  What are the.
Conceptual Overview 7 step design Chapter 4 Database Design for Mere Mortals.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
Software Life Cycle Model
Database System Development Lifecycle
Introduction to Computer Technology
CIS 321—IS Analysis & Design
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
MSIS 630: Week 13 System Implementation and Support
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Appendix D McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
ITEC224 Database Programming
Introduction to information systems
IST 210 Database Design Process IST 210 Todd S. Bacastow January 2005.
1 Chapter 9 Database Design. 2 2 In this chapter, you will learn: That successful database design must reflect the information system of which the database.
Week 4 Lecture Part 3 of 3 Database Design Samuel ConnSamuel Conn, Faculty Suggestions for using the Lecture Slides.
End HomeWelcome! The Software Development Process.
Lecture 3 Software Engineering Models (Cont.)
 System Development Life Cycle System Development Life Cycle  SDLC Phases SDLC Phases Phase 1: Preliminary Investigation Phase 2: Feasibility Study.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
WATERFLL MODEL Presented by.. Shiva Krishna Santhosh Chandra Varsha nihanth Aparna Archana Anusha.
IFS310: Module 13 Implementation and Support - Construction, Conversion and Maintenance of the New System.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
CISB113 Fundamentals of Information Systems IS Development.
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
Chapter 2: Testing in Software Life Cycle MNN1063 System Testing and Evaluation.
Day 3 in the pmProject Management Project Management (PM) ADJUST.
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Unit 17: SDLC. Systems Development Life Cycle Five Major Phases Plus Documentation throughout Plus Evaluation…
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
1-1 © Prentice Hall, 2004 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Prepared by: Arjaa Salem Makkawi ID: Sec : 2.
The information systems lifecycle Far more boring than you ever dreamed possible!
What Is Software Development? Software development is the way of creating software via successive levels in the arranged means. This method includes.
MANAGEMENT INFORMATION SYSTEM
Requirements Determination
System.
The Development Process of Web Applications
Software Process Activities.
Classical Waterfall Model
Life Cycle Models PPT By :Dr. R. Mall.
Chapter 6 Database Design
Manfred Huber Based on an earlier presentation by Mike O’Dell, UTA
IS442 Information Systems Engineering
SDLC The systems development life cycle is the foundation for many systems development methodologies such as RAD and agile Systems development life cycle.
Introduction to Systems Analysis and Design
Software Engineering Lecture #14.
Database Development Cycle
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
UNIT No- III- Leverging Information System ( Investing strategy )
Requirements Engineering
What is a System? A system is a collection of interrelated components that work together to perform a specific task.
Presentation transcript:

Prepared by : Dinesh Bajracharya Nepal Information System Development

Information System is designed and developed for organizations to address information requirement of the organizations. Organizations can ask software developers to design and develop information system for them.

What should be known to develop IS? For what purpose Information System is required? What are the information need of the organization? Who are the users of the Information system

Information systems can be developed as a single complete product or as increments which are integrated to form a single complete product. Information system can be developed as a single complete product if all the information needs of the organization is known at the beginning and the new information requirements will not occur in future. If all the information requirements are not known initially, and there is possibility of requirement changing the information system developed as increments would be better.

What ever information system development process used, they have some phases in common: Requirement gathering and analysis System Design System Development System Testing System Implementation System Evolution Backtracking from one phase to another is possible

Requirement gathering and Analysis This is the first phase or step in the information system development. In this phase information requirement of the organization is collected Requirements can be collected:- Enterprise analysis Strategic (Critical success factors) analysis Collected requirements are analyzed, feasibility analysis is preformed

System Design After the requirement gathering and analysis, if the development of Information system is feasible, then the Design of System is initiated. In system design, all objects involved in the system, their relationships with each other, their functions, interactions with each other etc are shown in the pictorial form Database (collection of interrelated data) is designed User Interface (UI) is designed.

System Development The system design is used to development system. That is design is converted into the program using one or more programming language Data Structures are defined Modules are implemented User interfaces (UI) developed Integration of UI and database is done

System Testing Data is prepared for system testing The developed system is tested to see if there is any error or problems Whether users requirements are met or not If test fails that is errors are found Uses requirements not meet Errors are corrected, unmet user requirements are met

System Implementation Error free and workable Information system implemented in the organization for working Can be implemented in parallel with existing system Can be implemented alone

System Evolution Users Requirements will change with time Those new requirements must be adjusted or addressed into the information system Change may have to bring into the information system