Escolar Documentos
Profissional Documentos
Cultura Documentos
CIS 105
Topics
List and describe the classic functions of managers: planning, organizing, directing, and controlling Define system, analysis, and design Describe the principal functions of the systems analyst List and describe the phases of the systems development life cycle (SDLC) Describe various data-gathering and analysis tools List and describe various system testing methods List and describe various system conversion methods
2
Levels of Management
Strategic level
Long range Primary function: planning Primary functions organizing and staffing Primary functions directing and controlling
4
Tactical level
Operational level
Systems
Analysis
Design
Analysis - Studying an existing system to determine how it works and how it meets users needs
Typically happens as a result of some impetus for change, combined with the authority to make the change
Design - The process of developing a plan for an improved system, based on the result of the systems analysis
6
Users
Users are individuals that use a system to perform their jobs. Users provide insight to the day-to-day business operations. Users must be included from the beginning to the end so that they will feel some sense of ownership of the new system when it is implemented.
8
Who Participates?
Project Team
Coordination of many people, tasks, and schedules Communication skills, both oral and written Planning and design (an analytical mind) Self-discipline and self-direction Good organizational skills Creativity
10
Recommendation
13
Phase 2: Analysis
What is the definition of Analysis?
Studying an existing system to determine how it works and how it meets users needs.
What needs to occur so an analyst can determine how the current system works?
Gather and analyze data From these findings, the system requirements for the new system can be determined.
14
Questionnaires Observation Many of the reports, diagrams, and documentation are entered into the Project Notebook, Dictionary, and/or Repository. 15
Data Analysis
During this stage the problem definition is refined. A detailed list of system requirements is created without regard to any specific hardware or software Typical tools to represent data and procedures:
Entity Relationship Diagram (ERD) Data Flow Diagram (DFD) Decision table/Decision Tree
Phase 3: Design
The new system is actually planned Divided into two sub-phases Preliminary design
High-level design Decide to Build or Buy
18
Build or Buy?
Build Software Customized Developed in-house Developed by outside vendor Prototyping limited function if any; shows what system may look like.
Buy Software Prepackaged software Select software vendor Customization may be offered by software vendor for a price
Phase 4: Development
Scheduling
Define tasks and schedule Use project management software to plan human resources and dependencies (see next slide).
Develop actual programs that make up the system Each program is tested by the programmer.
Programming
Testing
Use various tests to evaluate entire system (Testing slide coming up)
20
Project Management
The process of planning, scheduling, and controlling activities Set scope (goal, objectives, expectations) Activities and Deliverables to be completed The order activities occur (some activities are concurrent and others are dependent) Gantt Chart Time and cost estimates
21
Testing Types
Perform testing with predefined test data. Unit testing verifies that individual program units work. System testing determines whether all program units work together as planned. Volume testing uses real data in large amounts to see if system can handle it. Load testing used to determine if system can handle large number of concurrent users.
22
Phase 5: Implementation
Training hands-on and user manuals Equipment conversion allow for delivery and installation File conversion manual to electronic, or systems old format to new format Auditing - need to be able to track data in system back to the source. Evaluation does system meet original requirements, benefits, and budget? Maintenance Fix bugs, enhancements, and new regulations 23 System conversion (see next slide)
26
PPT 2
Key Ideas
Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization. The primarily goal is to create value for the organization.
1 - 27
Key Ideas
The systems analyst is a key person analyzing the business, identifying opportunities for improvement, and designing information systems to implement these ideas. It is important to understand and develop through practice the skills needed to successfully design and implement new information systems. 1 - 28
1 - 29
1 - 30
Project Phases
Planning (Why build the system? How should the team go about building it?) Analysis (Who uses system, what will it do, where and when will the system be used?) Design (How will the system work?) Implementation (System delivery)
1 - 31
1 - 32
Planning
Identifying business value Analyze feasibility Develop work plan Staff the project Control and direct project
1 - 33
Analysis
Analysis strategy Gathering business requirements Requirements definition use cases Process modeling Data modeling
1 - 34
Design
Design selection Architecture design Interface design Data storage design Program design
1 - 35
Implementation
Construction
Program building Program and system testing
Installation
Conversion strategy Training plan Support plan
1 - 36
Product
System Request Feasibility Analysis Workplan System Proposal System Specification New System and Maintenance Plan
Analysis
Design
Implementation
1 - 37
1 - 38
What Is a Methodology?
A formalized approach to implementing the SDLC
Methodology Categories
Process-Centered Data-Centered Object-Oriented Structured Design Rapid Application Development Agile Development
1 - 39
1 - 40
Cons
Design must be specified on paper before programming begins Long time between system proposal and delivery of new system
1 - 41
1 - 42
Cons
Still Uses Paper Documents Sub-projects May Be Difficult to Integrate
1 - 43
1 - 44
Prototyping
Throw-away prototyping
1 - 45
1 - 46
Cons
1 - 47
1 - 48
Cons
Tendency to do Superficial Analysis Initial Design Decisions May Be Poor
1 - 49
Throwaway Prototyping
1 - 50
Cons
May Take Longer Than Prototyping
1 - 51
1 - 52
Cons
Requires Discipline Works Best in Small Projects
1 - 53