Management Information Systems Notes
Management Information Systems Notes
What is an IS Project? - A one time, scoped and time endeavour aimed at altering
business processes using one or more technologies
What are the reasons for pursuing IT - Fixing a problem or point of pain
projects? - Pursuing a business opportunity
- Catching up with competition
- Requirement (gov or reg body)
- Automating processes or redesigning them
What is business process management? - Continuous analysis and improvement of business processes
(IT)
- Improves things; continuously monitoring process
- IT is an enabler of it → enhances processes
- Not a project; always happening
Describe Business Process Automation - Create or adjust electronic workflows to match the improved
process maps
How are IT Systems Built? What are the *** steps and typologies follow steps in a certain order
four components of STEPS?
STEPS
- System Development Life Cycle (SDLC)
1) Planning
2) Analysis
3) Design
4) Implementation
Describe the planning component and it’s - WHY info system should be built
two steps. - HOW the project team will go about building it
- There are two steps:
1) Project initiation
- System’s business value to the organization is identified
- Will it lower costs or increase rev
2) Project management
- PM creates a work plan, staffs projects, and using techniques to
help project ream control & direct project through entire SDLC
What are the four components of analysis? 1) WHO will use the system
What does the project team do in this 2) What the system will do
stage? 3) Where it will be used
4) When it will be used
- Project team:
- Investigates (any) current systems
- Identifies improvement opportunities
- Develops a concept for new system
Describe what happens in the design - How system operations in terms of the:
phase - Hardware, software, and network infrastructure
- User interface, forms, and reports that will be used
- Specific programs, database, and files that will be
needed
Describe the implementation phase - System is either developed or purchased (in the case of
packaged software) and installed
- Phase is the longest and most expensive part of entire process
3) Agile
- Engineer
- Scientist
2) Managerial Side (Business Analysis)
- Business analyst
- Requirements analysis
- Change management analysis (other titles too)
- PM
When is the feasibility analysis completed - You must continue assessing it throughout the project
What are the two types of costs and - Development & operational costs
benefits that should be considered? - Tanginble & intangible benefits
What is used for the cost-benefit analysis - Discounted cash flow method
using NPV? - NPV
What is the focus on strategic alignment - Are project goals aligned with business strategy?
with respect to organizational feasibility? - Close alignment with strategy increases the likelihood of
success
What are the three typlogies for SDLC? 1) Structured Systems Development
List the methods that fall under these - Waterfall, parallel development and v model
typologies 2) Rapid Application Development
- Iterative development, system prototyping, throw-away
prototyping
3) Agile
- Extreme programming (XP), scrum
Describe throwaway prototyping - Experimenting with design options that are thrown away
- Learning is factored into final version
Describe system prototyping - Quick & rough system version that “grows” with repetitive
refinements
- Version is refined
What does the agile methodology focus - Short cycles that produce a complete software product
on? - Highly adaptable in dynamic environments
→ Extreme Programming (XP), Scrum, - Cyclical typology
Others
→ Lower CASE
- Support technical side
- Implementation side
Explain project estimation - Estimate timing for each step in SDLC (and sub steps)
- Use industry-standard %
- Moderate Improvements
- Duration analysis
- Activity-based costing
- Information benchmarking
- BPI- Business Process Improvement
- Major Improvements
- Outcome Analysis
- Technology Analysis
- Activity elimination
- BPR- business process re-engineering
Describe what problem analysis is & explain a - Ask users to identify problems & solutions
drawback - Improvements tend to be small & incremental
- Rarely find improvements with significant business
value
Describe what root cause analysis is - Challenge assumptions about why problem exists
- Trace symptoms to their causes to discover “real
problem”
- 5 Whys
- Don’t want to miss the cause and only
see symptom
- Activity-based costing
- Bottleneck in terms of money
- Informal benchmarking
- Compare yourself to best in the market & see
which changes can be made to current
processes
What is the goal when analysis for major - Goal is to redesign of business process
improvements is done and what can be - Expect significant impact & value to an
expected? organization
- Activities focus on envisioning the business in new
What are the three types of activities and what ways
do they focus on? - Outcome analysis
- Focus on desirable outcomes from
customer POV
- Technology analysis
- Brainstorm opportunities fro important
& intersting technologies
- Activity elimination
- Challenge the importance of each
activity in process
- What if its removed?
- Technology analysis
- Brainstorm opportunities fro important
& intersting technologies
- Activity elimination
- Challenge the importance of each
activity in process
- What if its removed?
What is requirement determination? - Created a detailed precise list of what system should
do & system characteristics
2) User requirements
- What the user needs to do
3) System requirements
- How the system should be built
4) Functional requirements
- What the software should do
5) Non-functional requirements
- Characteristics system should have
2) Performance
- Speed, capacity, and reliability of system
- System should support 300 simultaneous users
from 9- 11 am, and 150 all other times
3) Security
- Who has authorized access to system under what
circumstances
- Only direct managers can see staff personnel
records
Lower CASE
- IT side
What does a requirements definition report look
like?
What are important things to keep in mind when - Use word “shall”
writing requirements? - The system shall open the train doors once
the train speed is at 0
- Verifiable
- Smallest testable unit
- Note difference between validation and
verification
- Unambiguous- simple English
- One interpretation
- Consistent- no set of requirements in conflict
Quick Quiz 1) Non- verifiable → can’t define whats good
1) Is this requirement verifiable: “This 2) Non-verifiable → what does usually mean?
system shall have a good human 3) Non-verifiable → what’s an infinite loop? cant verify
interface” 4) Non-functional
2) Is this a verifiable requirement: “The 5) Functional → system should be able to do that
report shall usually be generated within
10 seconds”
3) Is this a verifiable requirement: “The
program shall never enter an infinite
loop”
4) The system shall operate in a Linux
environment
5) The system shall display current
inventory levels in each store location
Describe what JAD is and its main goal - GOAL: produce complete requirements definition
document
- Extensive, structured group process
- Directly involves project sponsor, key managers, key
users
- Requires trained facilitator
- Expensive but valuable
What are Use Cases used for? - Express user requirements → interactions
- Users POV
- All tasks users need to perform during system
What is the external (functional) view? - Include most functional requirements if well
constructed
What are four benefits of use cases? - Derive functional requirements and also test cases
- User activities and system’s response to them
- Places user at center- heavy user involvement
- Analysts better understand application
domain
- Permits early drafting of functional tests
- Helps implement priorities
- Avoids unnecessary functionality
- Useful to identify
- Exceptions
- Special cases
- Error handling
Enter one functional requirement for McDonald’s - System shall store information (x minutes) until
self-order kiosk employee customer finishes entering order
- System shall transmit orders to back end for other
employees to access
- System shall authenticate payment method
- User shall add items to cart
- User shall confirm payment
How should you name a use case? - Reflect actor’s goal from actor’s perspective
- Describe a valuable transaction
- Examples:
- Reserve rental car
- Print invoice
- Register for payroll deduction
Normal course
- Main steps of the use case
Post conditions
- State after the use case
- Connection with subsequent use cases in sequence
When should you use a fully dressed format? - User reps are not engaged throughout whole
development process
- Complex/ high risk applications
- Teams need detailed & shared understanding of
user requirements
What are other sections that can be added in use - Frequency of use
cases? - Business rules
- Assumptions
- Notes/ issues
What are Use Case Models/ Diagrams useful for? - Define functional requirements/ use cases
- System context and basic flow of events
- 4 data stores
- Aystem 0: system leve
- Decompose system 0 into context 0?? MC DFD Decoomposition
- At level 0, its an integer
- Process number 34- its level 0
- If its 3.1 then its level 1
- Its if 3.1.2 then its level 2