HIM 367
cloud computing
- software rented or licensed -access through internet or VPN - applications bought, installed, maintained by vendor - users pay per-use or month-to-month license - software & hardware are services - create 14 M jobs by 2015 (?) reasons for choosing: - frees internal IT staff - faster access to applications than internal development - lower cost access to corp-quality applciations CONCERNS: - reliability - security - compliance with government regulations
project planning activities
1. describe scope, alternatives, and feasibility 2. divide project into manageable tasks 3. estimate resources and create a resource plan 4. develop preliminary schedule 5. develop a communication plan 6. determine project standards & procedures 7. identifying and assessing risk 8. create a preliminary budget 9. develop a project scope statement 10 set a baseline project plan
Project execution activities
1. execute the baseline project plan 2. monitor project progress against the baseline project plan 3 manage changes in the baseline project plan 4. maintain project workbook 5. communicate project status
sources of software
1. information technology services firms (outsourcing) 2. packaged software providers 3. vendors of enterpise solutions software 4. cloud computing 5. open-source software 6 the organization itself when it develops software in
Primary reasons for systems development projects
1. take advantage of business opportunities (meaningful use incentives) 2. solve business problems. (modernize, digitize health records.)
Skills of a successful systems analyst
Analytical understand organizations problem solving skills system thinking Technical understand potential and limitations of technology Managerial manage projects, resources, risk & change Interpersonal effective written and oral communication skills
Prototyping
Building a scaled-down version of the desired information system key advantages: 1. it involves the user in analysis and design 2. It captures requirements in concrete, rather than verbal or abstract form prototyping may also be used to augument the SDLC a prototype of the final system may be developed early in analysis to help the analysts id what users want.
COCOMO
COnstructive COst MOdel method used to make estimates of project size and costs uses parameters derived from prior projects of differing complexity these parameters are used to predict human resource requirements for basic, intermediate, and complex systems.
Reuse approaches
Four: 1. Ad hoc Reuse low level low cost 2. Facilitated reuse low level low cost 3. managed reuse moderate moderate cost 4. designed reuse high level high cost
Systems analysis
Phase of the SDLC in which the current system is studied and alternative replacement systems are proposed
Operation
Second part of 4th phase of the SDLC users find bugs programmers make changes for users and modify the system to reflect changing business conditions
SDLC
Series of steps used to mark the phase of development for an information system.
Systems Analyst
The org role most responsible for the analysis and design of info sys
network diagram
a diagram that depicts project tasks and their interrelationships shows dependencies between tasks shows which tasks can be done in parallel show slack time by data in rectangles
agile methodologies
a family of development methodologies characterized by short iterative cycles and extensive testing; active involvement of users for establishing , prioritizing, and verifying requirements; and a focus on small teams of talented experienced programmers Focuses on adaptive methodologies people instead of roles self-adaptive development process
system
a group of interrelated procedures used for a business function, with an identifiable boundary, working together for some purpose.
constraint
a limit to what a system can accomplish. some are imposed inside the system (limited # of staff) imposed by environment (due dates or regulations) a system takes input from its environment in order to function.... a system returns output to its environment as a result of its functioning and thus achieves its purpose. the system is constrained if electrical power is cut.
critical path scheduling
a scheduling technique in which the order and duration of a sequence of task activities directly affect the completion date of a project.
project charter
a short, high-level document prepared for both internal and external stakeholders to formally announce the establishment of the project and to briefly describe its objective, key assumptions, and stakeholders.
systems development methodology
a standard process followed in an organization to conduct all the steps necessary to analyze, design, implement and maintain information systems.
Enterprise Resource Planning System (ERPs)
a system that integrates individual, traditional business functions into a series of modules so that a single transaction occurs seamlessly within a single information system rather than several separate systems Benies: single repository for all aspects of a business process flexibility of modules Baddies: complex implementation reliance upon consultants business processes may have to change
participatory design (PD)
a systems development approach that originated in northern Europe, in which users and the improvement of their work lives are the central focus.
Program evaluation review technique (PERT)
a technique that uses optimistic, pessimistic, and realistic time estimates to calculate the expected time for a particular task.
Deliverable
an end product in a phase of SDLC
Component
an irreducible part or aggregation of parts that makes up a system; also called a subsystem
Project workbook
an online or hard-copy repository, for all project correspondence, inputs, outputs, deliverable, procedures, and standards, that is used for performing project audits, orienting new team members. communicating with management and customers, identifying future projects, and performing post project reviews
resources
any person, group of people, piece of equipment, or material used in accomplishing an activity
Techniques
are processes that you, as an analyst, will follow to help ensure that your work is well thought-out, complete, and comprehensible to others on your project team Provides support for a wide range of tasks, including conducting thorough interviews w/ current and future uses of the information system to determine what the system should do Planning and managing the activities in a systems development project diagramming how the system will function and designing the reports, such as invoices, your system will generate for its users to perform their jobs.
In-House Development
complete system hybrid systems
Tools
computer programs, such as CASE tools that make it easy to use specific techniques.
interrelated
dependence of one part of the system on one or more other system parts
Feasibility study
determines whether the information system makes sense for the organization from an economic and operational standpoint
modularity
dividing a system up into chunks or modules a relatively uniform size.
environment
everything external to a system that interacts with the system
Systems implementation and operation
final phase of the SDLC in which the information system is coded, tested, and installed in the organization, and in which the information system is systematically repaired and improved.
Project management
four phases: 1. Initiating the project 2. Planning the project 3. Executing the project 4. Closing down the project
Open-Source Software
freely available includes source code maintained by individuals
Gantt chart
graphical representation of a project that shows each task as a horizontal bar whose length is proportional to its time for completion. - shows duration of tasks - shows time overlap between tasks - show s slack time
Repository
integrated, standard, centralized DB that contains all diagrams, forms and report definitions, data structures, data definition, process flows and logic, and definitions of the organizational and system components; it provides a set of mechanisms and structures to achieve seamless data-to-tool and data-to-data integration.
Systems Design
phase of the SDLC in which the system chosen for development in systems analysis is first described independently of any computer platform (logical design), and is then transformed into technology-specific details (physical design) from which all programming and system construction can be accomplished.
Project
planned undertaking of related activities, having a beginning and an end, to reach an objective.
interface
point of contact where a system meets its environment or where subsystems meet each other
Methodologies
sequence of step-by-step approaches that help develop the final product: the information system most incorporate several development techniques, i.e. direct observations and interview with users of the current system.
application software
software designed to process data and support users in an org., e.g. spreadsheets, word processors, and db management
Computer-aided software engineering (CASE)
software tools that provide automated support for some portion of the systems development process.
computer-aided software engineering (CASE)
software tools that provide automated support for some portion of the systems development process.
joint application design (JAD)
structured process in which users, managers, and analysts work together for several days in a series of intensive meetings to specify or review system req.
Project manager
systems analyst with diverse set of skills --- management leadership technical conflict management customer relationship ---- who is responsible for initiating, planning executing, and closing down a project
Rapid Application Development (RAD)
systems development methodology created to radically decrease the time needed to design and implement information systems. grew out of two trends increased speed and turbulence of doing business in the late 80s and early 90s and the ready availability of high =powered computer based tools to support systems development.
slack time
the amount of time that an activity can be delayed without delaying the project
cohesion
the extent to which a system or subsystem performs a single function
coupling
the extent to which subsystems depend on each other. depends on subsystems the best example is the control system, made up of the printed circuit board and its chips. Every function the MP3 player can perform is enable by the board and the chips
project closedown
the final phase of the project management process, which focuses on bringing a project to an end.
systems planning and selection
the first phase of the SDLC, in which an organization's total information system needs are analyzed and arranged, and in which a potential information systems project is identified and an argument for continuing or not continuing with the project is preserved.
project initiation
the first phase of the project management process in which activities are performed to assess the size, scope, and complexity. 1. establish initiation team 2. establish relationship w/ customer 3. establish project initiation plan 4. establish management procedures 5. establish the project management environment and the Project Workbook 6. Develop the Project Charter
boundary
the line that marks the inside and outside of a system and that sets off the system from its environment
outsourcing
the practice of turning over some or all of an organization's information systems applications and operations to an outside firm.
decomposition
the process of breaking the description of a system down into small components; also known as functional decomposition analyze smaller and less complex pieces that are easier to understand than larger, complicated pieces. Break system into small, manageable, and understandable subsystems Focus attention on one area (subsystem) at time, w/o interference from other areas Concentrate on the part of the system pertinent to a particular group of users, w/o confusing users with unnecessary details Build different parts of the system at independent times and have the help of different analysts
information systems analysis and design
the process of developing and maintaining an information system.
work breakdown structure (WBS)
the process of dividing the project into manageable tasks and logically ordering them to ensure a smooth evolution between tasks.
project planning
the second phase the project management process, which focuses on defining clear, discrete activities and the work needed to complete each activity within a single project.
Systems development life cycle (SDLC)
the series of steps used to mark the phases of development for an information system. 1. planning & selection 2. analysis 3. design 4. implementation and operation can return to an earlier phase, if necessary some analysts consider the life cycle to be a spiral, constantly cycling through the phases at different levels of detail.
critical path
the shortest time in which a project can be completed
Reuse
the use of previously written software resources, especially objects and components, in new applications. typically applied to two different development technologies: 1. object-oriented development 2. component-based development. changes made to the object class and not to applications
project execution
third phase of the project management process, in which the plans created in the prior phases (project initiation and planning) are put into action.
