Saturday, March 28, 2009

System Analysis lecture 3

This lecture covers the requirments gathering for the system developement
In this stage Analyst will study about the organization structure, business process and information flow. this stage called as fact finding also. The Analyst will conduct interviews with each level of people and he will gather information and he will come to know the information flow and communication of Information. This stage conatins 2 defining ways
1.Logical modeling

2.Physical modeling

Primary information gatherring techniques
build prototype working models.

Prototype working models
Conduct JAD sessions
research vendor solutions
observe and document business processes
Once the Analyst models each and every process, he will note down the functions what the new system should according to the procedures and business functions. In this stage Analyst shoud consider about the security measures also. People who are in new system

1.Users

2.Clients

3.Technical staff (Analyst will conduct interview wil each and every group of person) There are some techniques that Analyst follows while gathering requirments

1.Structural Approach - create model of existing system and gathers information of existing system
2.Current Approach - Identifying logical requirements and balancing the new system requirements This stage includes fact finding way also which means reviewing the old system reports, invoices, information flows, and forms etc and then the Analyst will gather how the information flows at current situation and he will know about the current rules and redundancies and understands the process. Another stage of requirment gathering is preparing checklist, this contents the current system functions and the the new system functions. and the additional things that new system should do. In this stage, the Analyst will conductt interviews with each people or group of people. This will bbe an expense for the organization, but the Analyst should get the correct information from the users.

Thursday, March 26, 2009

System Analysis lecture 2

This lecture mainly contains about the system development lifecycle and system design

The system developement and designing always should be well planned and have strong end point and these gives the organization to get the desired output.

The good analysing and designing gives reliable, robust and efficient system.

The lifecycle of system developement

*Planning - Understanding the problem and ensuring the feasibility and obtaining approval
*Analysing - Gathering the detail from ongoing process and getting the idea for the new system and knowing "What system should do?"
*Design - After analysing, getting an image of the organization structure and gathering the requirements.
*Implementation - In this stage all the program developement will be done ex - coding, testing, programming. and user training.
*Support/maintenence - After the Implementation of system, this stage will continues forever and this stage includes problem solving, system running and System maintenence.

The main models in system developement are

Flowchart, data flow diagram, Entity relationship diagram, usecase diagram and sequence diagram.

The main tools they used system developement
Project management application
Drawing tools
Computer aided software etc

There are two different approaches in system designing
1.Traditional approach
2.Structured Programming

System Analysis lecture 1

This lecture covers the Introduction of system analysing and designing

Systen analysis is very crucial to succeed in modern business, so the Analyst should have an overall knowledge of the organization structure, functions, functional workflow and their management techniques. The information system is a collection of many interelated components.

The System Analysis helps to

* Make the workflow effiency

*Helps to make business more competitive

System Analyst should consider in two areas

Which are system analysis and system design

System analysis means "What system should do"

System design means "How the system can be implemented physically" and this helps to solve business problems with it.

Analyst is a person who expertizes in more than one area. ex - programming, designing, networking, managerial, and technical areas and they mainly involves in special tasks such as business process reengineering.(These used to do radical improvement to system)