1. SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
1.1. PLANNING
1.1.1. identifies whether or not there is the need for a new system to achieve a business’s strategic objectives
1.1.2. a preliminary plan (or a feasibility study) for a company’s business initiative to acquire the resources to build on an infrastructure to modify or improve a service
1.1.3. The company might be trying to meet or exceed expectations for their employees, customers and stakeholders too
1.1.4. Resources, costs, time, benefits and other items should be considered at this stage
1.2. ANALYZE
1.2.1. where businesses will work on the source of their problem or the need for a change
1.2.2. possible solutions are submitted and analyzed to identify the best fit for the ultimate goal(s) of the project.
1.2.3. where system analysis takes place or analyzing the needs of the end users to ensure the new system can meet their expectations.
1.3. DESIGN
1.3.1. the necessary specifications, features and operations that will satisfy the functional requirements of the proposed system which will be in place.
1.3.2. is the step for end users to discuss and determine their specific business information needs for the proposed system. It"s during this phase that they will consider the essential components (hardware and/or software) structure (networking capabilities), processing and procedures for the system to accomplish its objectives.
1.4. DEVELOPMENT
1.4.1. marks the end of the initial section of the process
1.5. TESTING
1.5.1. involves systems integration and system testing (of programs and procedures)—normally carried out by a Quality Assurance (QA) professional—to determine if the proposed design meets the initial set of business goals.
1.5.2. Testing may be repeated, specifically to check for errors, bugs and interoperability
1.6. IMPLEMENTATION
1.6.1. when the majority of the code for the program is written
1.6.2. This step puts the project into production by moving the data and components from the old system and placing them in the new system via a direct cutover
1.7. MAINTENANCE
1.7.1. involves maintenance and regular required updates.
1.7.2. includes providing latest updates for certain components to make sure it meets the right standards and the latest technologies to face current security threats.
2. TYPES OF LIFE CYCLE
2.1. WATERFALL MODEL
2.1.1. Represents the system in terms of data and the processes that objects that act upon that data
2.1.2. System development is organized into phases with deliverables and milestones to measure progress
2.1.3. Changes can be costly, especially in later phases
2.1.4. Requirements are defined early, and can change during development
2.2. SPIRAL MODEL
2.3. ITERATIVE AND INCREMENTAL DEVELOPMENT
2.3.1. Develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental), allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system
2.4. AGILE MODEL
2.4.1. attempt to develop a system incrementally, by building a series of prototypes and constantly adjusting them to user requirements
2.5. PROTOTYPING MODEL
2.5.1. A prototype is an early working version of an information system
2.5.2. Prototyping tests system concepts and provides an opportunity to examine input, output, and user interfaces before final decision are made.
2.5.3. A prototype can serve as an initial model that is used as a benchmark to evaluate the finished system, or the prototype itself can develop into the final version of the system
2.6. RAPID APPLICATION DEVELOPMENT (RAD)
2.6.1. is a team-based technique that speeds up information systems development and produces a functioning information system
2.6.2. The RAD process allows users to examine a working model as early as possible, determine if it meets their need, and suggest necessary changes
2.7. JOINT APPLICATION DEVELOPMENT (JAD)
2.7.1. is a popular fact-finding technique that brings users into the development process as active participants
2.7.2. The JAD group usually has a project leader, who needs strong interpersonal and organizational skills, and one or more members who document and record the results and decisions
2.7.3. JAD can result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system
3. PROJECT MANAGEMENT DESCRIPTION
3.1. PLANNING
3.2. SCHEDULING
3.3. MONITIORING
3.4. REPORTING
4. what is INFORMATION SYSTEM
4.1. DEFINTION
4.1.1. Information
4.1.1.1. Is data that has been transformed into output that is valuable to users
4.1.1.2. Example : an order processing system that displays an order form
4.1.2. Information System
4.1.2.1. Combines information technology, people and data to support business requirements
4.1.2.2. Information System have 5 components which are hardware, software, data, processes and people
4.2. COMPONENTS of Information System
4.2.1. Hardware
4.2.1.1. Is the physical layer of the information system
4.2.2. Software
4.2.2.1. System software
4.2.2.2. Application software
4.2.2.3. Enterprise applications
4.2.3. Data
4.2.3.1. Tables store data
4.2.3.2. Linked tables work together to supply data
4.2.4. Processes
4.2.4.1. Describe the tasks and business functions that users, managers, and IT staff members perform to achieve specific results
4.2.5. People
4.2.5.1. Stakeholders
4.2.5.2. Users, or end users
4.3. TYPES of Information System
4.3.1. Executives
4.3.1.1. Executive Information Systems
4.3.2. Senior Managers
4.3.2.1. Decision Support Systems
4.3.3. Middle Managers
4.3.3.1. Management Information Systems
4.3.4. Workers
4.3.4.1. Transaction Processing Systems
5. SYSTEM DEVELOPMENT APPROACH
5.1. METHOD
5.1.1. Structured Analysis
5.1.1.1. Is a traditional systems development technique that is time tested and easy to understand
5.1.1.2. Uses a series of phases to plan, analyze, design, implement and support an IS
5.1.2. Object Oriented Analysis
5.1.2.1. is a popular technical approach for analyzing, designing an application, system
5.1.2.2. or business by applying the object-oriented paradigm and visual modeling throughout the development life cycles to foster better stakeholder communication and product quality
5.1.3. Agile/Adaptive Method
5.1.3.1. refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner
6. UNDERSTAND PROJECT MANAGEMENT
6.1. Explanation on Project
6.1.1. PLANNING
6.1.2. SCHEDULING
6.1.3. MONITORING
6.1.4. REPORTING
6.2. STEPS in Project Planning
6.3. DESCRIPTION ABOUT
6.3.1. WORK BREAKDOWN STRUCTURES
6.3.1.1. involves breaking a project down into a series of smaller tasks
6.3.1.2. A work breakdown structure must clearly identify each task and include an estimated duration. A task, or activity, is any work that has a beginning and an end and requires the use of company resources such as people,time, or money
6.3.2. TASK PATTERNS
6.3.2.1. Tasks in a work breakdown structure must be arranged in a logical sequence called a task pattern
6.3.3. CRITICAL PATH ANALYSIS
6.3.3.1. A critical path is a series of tasks which, if delayed, would affect the completion date of the overall project. If any task on the critical path falls behind schedule, the entire project will be delayed
6.3.3.2. Project managers always must be aware of the critical path, so they can respond quickly to keep the project on track