# data[].attributes.headline
Cost / Economic feasibility (i.e. the financial cost)Approximated, “back-of-the-envelope” analysisPurpose: eliminate infeasible ideas as soon as possibleSchedule feasibility (i.e. the timetable)Difficult to determine but a rough estimate is neededTechnical feasibility (i.e. can we build/run/maintain this)Is the proposed system able to be built using existing information technology?Organisational / cultural feasibility (i.e. will the staff use this)Does the proposed system fit the customs, culture, charter and legal requirements of the organisation?Legal feasibility - Measures how well a solution can be implemented within existing legal and contractual obligations

# data[].attributes.subject
Cost / Economic feasibility (i.e. the financial cost)Approximated, “back-of-the-envelope” analysisPurpose: eliminate infeasible ideas as soon as possibleSchedule feasibility (i.e. the timetable)Difficult to determine but a rough estimate is neededTechnical feasibility (i.e. can we build/run/maintain this)Is the proposed system able to be built using existing information technology?Organisational / cultural feasibility (i.e. will the staff use this)Does the proposed system fit the customs, culture, charter and legal requirements of the organisation?Legal feasibility - Measures how well a solution can be implemented within existing legal and contractual obligations

# data[].attributes.body
The sequential phases in Waterfall model are:

Requirement Gathering and analysis: All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification doc.

System Design: The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture.

Implementation: With inputs from system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality which is referred to as Unit Testing.

Integration and Testing: All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.

Deployment of system: Once the functional and non functional testing is done, the product is deployed in the customer environment or released into the market.

Maintenance: There are some issues which come up in the client environment. To fix those issues patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

# data[].attributes.body
Technical, Economic, Legal, Operational, planing, resources, financial

# data[].attributes.headline
A systems analyst’s (or business analyst’s) role is to define (or specify)a new or modified system (usually computer-based). The analyst’s endproduct may be called an External System Design (ESD), FunctionalSpecifications, or Detailed User Requirements. It must be: understood in complete detail and approved by responsible userrepresentatives, understood and accepted by prospective developers (or softwareproduct purchasers).A system designer uses that end product, the ESD, as the startingpoint for specifying software (programs, object-oriented classes, files,and databases) that will satisfy those requirements.Recent fad methodologies combine the two roles into an incrementalapproach in which the specifications emerge as user representativesand developers alternate between discussing and implementing fragmentsof the desired application. This approach may work well forvery small applications.A short summary: The analyst specifies WHAT the proposed systemwill do; the designer specifies HOW the system will be organized andimplemented.

# data[].attributes.subject
A systems analyst’s (or business analyst’s) role is to define (or specify)a new or modified system (usually computer-based). The analyst’s endproduct may be called an External System Design (ESD), FunctionalSpecifications, or Detailed User Requirements. It must be: understood in complete detail and approved by responsible userrepresentatives, understood and accepted by prospective developers (or softwareproduct purchasers).A system designer uses that end product, the ESD, as the startingpoint for specifying software (programs, object-oriented classes, files,and databases) that will satisfy those requirements.Recent fad methodologies combine the two roles into an incrementalapproach in which the specifications emerge as user representativesand developers alternate between discussing and implementing fragmentsof the desired application. This approach may work well forvery small applications.A short summary: The analyst specifies WHAT the proposed systemwill do; the designer specifies HOW the system will be organized andimplemented.

# data[].attributes.body
Development,
Testing,
Implementation,
Maintenance

# data[].attributes.headline
Feasibility study is an assessment of the practicality of a proposed project or system. It aims to understand and assess the strengths and weaknesses of a new business venture, it takes into considerations opportunities and threats present in the environment, the resources required to carry through, and ultimately the prospects for success. In its simplest terms, the two criteria to judge feasibility are cost required and value to be attained.

# data[].attributes.subject
Feasibility study is an assessment of the practicality of a proposed project or system. It aims to understand and assess the strengths and weaknesses of a new business venture, it takes into considerations opportunities and threats present in the environment, the resources required to carry through, and ultimately the prospects for success. In its simplest terms, the two criteria to judge feasibility are cost required and value to be attained.

# data[].attributes.headline
business planning process: system definition, requirement analysis, development design, test, implementation, system maintance 

# data[].attributes.subject
business planning process: system definition, requirement analysis, development design, test, implementation, system maintance 

# data[].attributes.headline
5. Discuss the various types of feasibility studies. Why are they all needed?

# data[].attributes.subject
5. Discuss the various types of feasibility studies. Why are they all needed?

# data[].attributes.headline
4. Why is it important for everyone in business organisations to have a basic understanding of the systems development process?

# data[].attributes.subject
4. Why is it important for everyone in business organisations to have a basic understanding of the systems development process?

# data[].attributes.headline
3. What is the difference between systems analysis and systems design?

# data[].attributes.subject
3. What is the difference between systems analysis and systems design?

# data[].attributes.headline
1. Describe the phases/stages of the system development lifecycle as we have discussed in the lecture.

# data[].attributes.subject
1. Describe the phases/stages of the system development lifecycle as we have discussed in the lecture.