1. Computer-Aided Software Engineering (CASE)
1.1. the scientific application of a set of tools and methods to a software system which is meant to result in high quality, defect free, and maintainable software products.
1.2. Example
1.2.1. SYSTEM ANALYST - research the Visible Analyst CASE tool
2. Information Systems Projects
2.1. the coherent organization of the information required for an organization to execute projects successfully.
2.2. Main Reasons
2.2.1. Systems request
2.2.2. Improved service Support for new products and services
2.2.3. Better performance
2.3. Factors Affect
2.3.1. Internal Factors
2.3.1.1. Strategic plan
2.3.1.2. Top manager
2.3.1.3. User requests
2.3.2. External Factors
2.3.2.1. Technology
2.3.2.2. Suppliers
2.3.2.3. Customers
2.3.2.4. Competitors
2.3.2.5. The economy
2.3.2.6. Government
3. Evaluation of Systems Requests
3.1. Systems review committee or a computer resources committee to evaluate systems requests
3.2. Systems Requests Forms
3.2.1. A properly designed form streamlines the request process and ensures consistency
3.2.2. Occasionally a situation will arise that requires an immediate response
3.3. Systems Review Committees
3.3.1. large companies use a systems review committee
3.3.2. smaller companies rely on one person
3.3.3. The goal is to evaluate the requests and set priorities
4. STRATEGIC PLANNING
4.1. Strategic Planning Overview (SWOT)
4.1.1. STRENGTHS
4.1.1.1. internal attributes and resources that support a successful outcome.
4.1.1.2. What do other companies see as your strengths?
4.1.1.3. What are the strengths of your company?
4.1.2. WEAKNESSES
4.1.2.1. internal attributes resources that work against a successful outcome.
4.1.2.2. What are some weaknesses seen by other companies?
4.1.2.3. Areas you should avoid?
4.1.3. OPPORTUNITIES
4.1.3.1. external factors the project can capitalize on or use to its advantage.
4.1.3.2. What are the best opportunities?
4.1.3.3. Interesting trends in your niche?
4.1.4. THREATS
4.1.4.1. external factors that could jeopardize the project.
4.1.4.2. What is your competition doing?
4.1.4.3. Is there any outstanding debt or large loan?
4.2. FROM STRATEGIC PLANS TO BUSINESS RESULTS
4.2.1. Mission Statement
4.2.2. Stakeholders
4.2.3. Goals
4.2.4. Objectives
4.3. the process of identifying long term organizational goals, strategies, and resources
5. Overview of Feasibility
5.1. Operational Feasibility
5.1.1. proposed system will be used effectively after it has been developed
5.2. Technical Feasibility
5.2.1. technical resources needed to develop, purchase, install, or operate the system
5.3. Economic Feasibility
5.3.1. Total cost of ownership (TCO) - assessing costs,
5.3.2. Tangible benefits - decrease in expenses
5.3.3. Intangible benefits - Web site that improves a company's image
5.4. Schedule Feasibility
5.4.1. The first step in evaluating feasibility is to identify and weed out systems requests that are not feasible
6. Setting Priorities
6.1. Factors that Affect Priority
6.1.1. Will the proposed system reduce costs? Where? When? How? How much?
6.1.2. Will the system increase revenue for the company? Where? When? How? How much?
6.2. Discretionary Projects
6.2.1. management has a choice in implementing them
6.3. Nondiscretionary Projects
6.3.1. no choice exists
7. Preliminary Investigation Overview
7.1. An initial investigation to clearly identify the nature and scope of the business opportunity or problem
7.2. Steps
7.2.1. Step 1: Understand the Problem or Opportunity
7.2.2. Step 2: Define the Project Scope and Constraints
7.2.3. Step 3: Perform Fact-Finding
7.2.4. Step 4: Analyze Project Usability, Cost, Benefit and Schedule Data
7.2.5. Step 5: Evaluate Feasibility
7.2.6. Step 6: Present Results and Recommendations to Management