1. Dylan Clipp ITP 251 Final Presentation A Comprehensive Guide to Systems Analysis & Design
2. Software Used This Semester Visible Analyst Visual Paradigm Microsoft Project Open Work Bench Microsoft Access Microsoft Word Microsoft PowerPoint Microsoft Excel
3. Ch. 1- Information Systems Components Information System Components Hardware, Software, Data, Processes, People The System Analyst Position The system analysts job overlaps business and technical issues. It is a very broad ranged job. They help translate business requirements into IT projects. A system analyst plans projects, develops schedules, and estimates costs. He also conducts meetings, delivers presentations, and writes memos, reports, and documentation.
4. Chapter 2: Analyzing the Business Case Strategic Planning Swot Analysis: During strategic planning, managers ask questions to known as a SWOT analysis because it examines the company’s strengths(S), weakness (W), opportunities (O), and threats (T). Business Case: A business case refers to the reasons, or justification for a proposal.
5. Chapter 2: (cont) Information System Projects: Starting point for most projects is known as “System Request”, which is a formal way of asking for IT support. The main reasons for systems requests are improved service to customers, better performance, support for new products and services, and more information, stronger controls, and reduced costs. A systems review committee will then determine the systems requests, and based off of feasibility, and priority they will determine whether or not to grant request.
6. Preliminary Investigation Report Step 1: Understand the problem or opportunity Step 2: Define the project scope and constraints. Step 3: Perform fact-finding Step 4: Analyze project usability, cost, benefit, and schedule data Step 5: Evaluate feasibility Step 6: Present results and recommendations to management
7. Chapter 3: Managing Systems Projects Project management: Planning: identify project tasks and estimating completion time and costs Scheduling: creation of a timetable, usually in chart form, and shows tasks, task dependencies, and critical tasks that might delay the project. Gantt/Pert Monitoring & Controlling: guiding, supervising, and coordinating the project team’s workload. Project Reporting: regular progress reports to management, users, and project team.
9. Chapter 3: Risk Management Risk Management: Develop a risk management plan Identify the risks Analyze the risks Create a risk response plan Monitor Risks.
10. Chapter 4: Requirements Modeling System Analysis Phase: overall objective is to understand the proposed project and ensure that it will support the business requirements, and build a solid foundation for system development. A system requirement is a characteristic or feature that must be included in an information system to satisfy business requirements and acceptable to users. Requirements Modeling: fact-finding to describe the current system and identification of the requirements for the new system. (Outputs, inputs, processes, performance, security)
11. Ch.4 (cont)Team Based Techniques Joint Application Development (JAD): Fact finding technique that brings users into development process as active participants. Rapid Application Development(RAD): Users involved every step of the way. Provides a fast track approach to a full spectrum of system development tasks. Agile Methods: represents a recent trend that stresses intense interaction between system developers and users.
12. Ch. 4 (cont) UML Unified Modeling Language (UML): method of visualizing and documenting software system design. Uses object oriented design concepts.
13. Ch. 4 (cont) Modeling Techniques Data Flow Diagram Use Case Diagram Visually represents the interaction between users and information system. Uses actors and roles. Shows how the system stores, processes, and transforms data.
17. Chapter 5: Data Process and Modeling Data Flow Diagrams: use various symbols to show how the system transforms input data into useful information. Data Dictionary: central storehouse of information about a system’s data. Analyst will use the data dictionary to collect, document, and organize specific facts about the system, including data flows, data stores, entities, and processes.
18. Ch. 5(cont) Decision Tables/Trees: Show logical structure with all possible combinations of conditions and resulting actions. Often used to describe a logical process to ensure that you have not overlooked any logical possibility.
19. Chapter 6: Object Modeling Object Oriented Analysis: Describes an information system by identifying things called objects. Objectsrepresent real persons, place, event, or transaction. The end process of object-oriented analysis is an object model. Attributes: characteristics that describe the object. Method: tasks or functions that the object performs Message: command to perform certain task or function.
20. Ch. 6(cont) Classes Classes: Objects belong to a group or category called a class. All objects within a class share common attributes & methods. The class is a blueprint, or template for all the objects within the class. Subclasses: more specific categories within a class. Super class: a more general category of a class.
21. Ch. 6(cont) Object Relationship Diagram: Relationship diagram that will provide an overview of the system.
22. Ch. 6(cont) State Transition Diagram: Shows how an object changes from one state to another, depending on events that affect the object.
23. Ch. 6(cont) Activity Diagram: resembles a horizontal flowchart that shows the actions and events as they occur.
24. Chapter 7: Development Strategies Software as a Service (SaaS): a model of software deployment where an application is hosted as a service provided to customers over the internet. Traditional Development: Development typically follows one of three main paths: in-house development, purchase of a software package with possible modification, or use of outside consultants. Web-Based Development: Systems are developed and delivered in a internet-based framework such as .NET or WebSphere. Cloud Computing: Ultimate form of SaaS. Allows a large group of users to tap into power of the cloud, with all the computers in the cloud sharing your processing and overhead. Outsourcing: is the transfer of information systems development, operation, or maintenance to an outside firm that provides these services for a fee on a temporary or long term basis. In House Development: when a company decides to develop its own systems, or software.
25. Ch. 7(cont) Analyzing Cost Benefit: Payback Analysis: determines how long it takes an information system to pay for itself through reduced costs and increased benefits. Return on investment (ROI) is a percentage rate that compares the total net benefits (the return) received from a project to the total costs(the investment) of the project. Net Present Value(NPV): the total value of the benefits minus the total value of the costs, with both costs, and benefits adjusted to reflect the point in time at which they occur. System Requirements Document: contains the requirements for the new system, describes the alternatives that were considered, and makes a specific recommendation to management.
26. Ch. 7(cont) Analyzing Cost Benefit: System Requirements Document: contains the requirements for the new system, describes the alternatives that were considered, and makes a specific recommendation to management. To view my Systems Requirement Document you can find it by clicking here: http://tinyurl.com/23s77j9
27. Chapter 8: Output &User Interface Design Printed and Screen Output: Detail Reports, Exception Reports, Summary Reports, Output Security: protects privacy rights and shields the organizations proprietary data from theft or unauthorized access. User Interface Design: User Interfaces describe how users interact with a computer system, and consists of all the hardware, software, screens, menus, functions, output, and features that affect two-way communications between the user and computer. Input Design: Quality of output is only as good as the quality of the input. Main objective is to ensure the quality, accuracy, and timeliness of input data.
28. Chapter 9: Data Design Data Structure is a framework for organizing and storing data in an information system. Files or tables contain data about people, places, things, or events that interact with the information system. Done through a file processing system, inside of a database system. DBMS Components: Users: typically work with predefined queries and switchboard commands to access the stored data. Database Administrators: responsible for a DBMS management and support. Related Information Systems: a DBMS can support several related information systems that provide input to, and require specific data from, the DBMS. Normalization: the process of creating table designs by assigning specific fields or attributes to each table in the database.
29. Ch. 9(cont) Entity Relationship Diagram: a model that shows the logical relationships and interaction among system entities. Provides an overall view of the system and provides a blueprint for creating the physical data structures
30. Chapter 10: System Architecture System Architecture Checklist: Enterprise resource planning(ERP): objective of ERP is to establish a company-wide strategy for using IT resources. Initial and total cost of ownership (TCO): Go back and review initial TCO and you see if moving forward how it will change and what or where you can make improvements. Scalability: refers to a system’s ability to expand, change, or downsize to meet the changing needs of a business enterprise. Web integration: Any applications that the information system includes will need to be implemented to handle input and provide the required output. Legacy system interface requirements: Determines whether or not the new system will have to interface with one or more of the older systems that typically run on mainframe computers. Processing options: designers consider how the system will process the data, the security issues that go behind it. Security issues
31. SYSTEM DESIGN SPECIFICATION System Design Specification: a document that presents the complete design for the new information system, along with detailed costs, staffing, and scheduling for completing the DSLC phase—Systems implementation. To view my System Design Specification Document click here: http://tinyurl.com/23oxdcl
32. Chapter 11: Managing Systems Implementation Involves application development, testing, documentation, training, data conversion, system change over, and post-implementation evaluation of the results. Turns all the design work into a functioning project. Software Quality Assurance: ISO: International Organization for Standardization Application Development: Planning -> Integration Testing -> System Testing -> Documentation Agile Application Development: Uses a highly interactive process. Development teams are constantly communicating with the customer or primary user to shape and form the system to match the customer’s specifications. Based on a quick and nimble development process that easily adapts to change.
33. Chapter 12: Managing Systems Support & Security Involves three main concerns: User expectations, system performance, and security requirements. User Support: User Training: initial training performed when a new system is introduced. Help Desks: centralized resource staffed by IT professionals who provide users with support they need to do their jobs. Maintenance Tasks: Corrective Maintenance: diagnoses and corrects errors in an operation system. Adaptive Maintenance: adds a new capability and enhancements Perfective Maintenance improves efficiency Preventative Maintenance: reduces the possibility of future system failure. Maintenance Team: System Administrator: Manages computer and network Systems. System Analysts: investigate and rapidly locate the source of problems by sing analysis and synthesis skills. Programmers: Tend to work on something specialized developing applications or programs for companies.
