Sunteți pe pagina 1din 37

Need for System Analysis

System development life cycle is a phased approach to analysis and design that holds the systems which are best developed through the use of a specific cycle of the analyst and user activities. The steps include
Identifying problems, opportunities and objectives Deciding information requirements Frequency of information Analyzing the need of the system

Designing of the recommended system


Developing of the system Documentation Testing and maintenance of the system Implementation and evaluating the system

THE SYSTEMS APPROACH TO PROBLEM SOLVING


System problem solving is the act of studying a problem environment in the order to implement corrective solutions that take the form of new or improved systems- The general problem solving steps are Planning : Identify the scope and boundary of the problem and plan the development strategy and goals. Analysis : Study and analyze the problems, causes and effects. Then, identify and analyze the requirements that must be fulfilled by any successful solution. Design : if necessary, design the solution not all solution require design. Implementation : Implement the solution Support : Analyze the implemented solution, refine the design and implement improvements to the solution. Different support situations can thread back into the previous steps.

THE SYSTEMS APPROACH


The systems approach to problem solving used a systems orientation to define problems and opportunities and develop solutions. Studying a problem and formulating a solution involve the following interrelated activities:

Recognize and define a problem or opportunity using systems thinking. Develop and evaluate alternative system solutions.

Select the system solution that best meets your requirements.


Design the selected system solution. Implement and evaluate the success of the designed system

DEFINING PROBLEMS AND OPPORTUNITIES SYSTEMS THINKING DEVELOPING ALTERNATIVE SOLUTIONS EVALUATING ALTERNATIVE SOLUTIONS SELECTING THE BEST SOLUTION DESIGNING AND IMPLEMENTING A SOLUTION POST IMPLEMENTATION REVIEW

STAGES IN SYSTEM ANALYSIS


System analysis is an in-depth study of end-user information requirements that is needed before the design of a new information system can be completed. System analysis analyses in detail : The components and requirements of a system The information needs of an organization The characteristics and components of presently utilized information system, and

The functional requirements of proposed information system

Broadly classified as
Organizational Analysis

Analysis of the Present System


Functional Requirement Analysis

Structured SAD(SSAD)
This process development process made up of five modules that include tasks, which can be combined into step by step procedures. The below figure illustrates the five modules that make up SSADM. It follows the basic process of the linear cycle. It goes through concept formation and feasibility analysis, and then develops an analysis model followed by system specification, then a logical design and finally physical implementation. These activities are divided into modules that roughly correspond to the development phases.

System Development Model


Usage of System Development Model is a standard process followed in an organization to conduct all the steps necessary to analyze, design, implement and maintain information system. Various models are used for system development. System development is conceiving, designing, and implementing a system. Developing information system is by a process of investigation, analysis, design, implementation and maintenance. System development tools are graphical, textual and computer aided tools and techniques which are used to help analyze, design and document the development of an information system.

The Waterfall Model


The waterfall model is believed to have been the first process model which was introduced and widely followed in software engineering. The innovation was that the first time software engineering was divided into separate phases. As programs became bigger the need for a better requirements phase, some more thoughts on the design, etc.

The phases of "The Waterfall Model" are:

Requirement Analysis & Definition System Design Software Design Software Integration & Verification System Verification Operation & Maintenance

The Spiral Model The process begins at the center position. From there it moves clockwise in traversals. Each traversal of the spiral usually results in a deliverable. It is not clearly defined what this deliverable is. This changes from traversal to traversal.

Prototype Model
The Prototype Model slowly builds from a simple concept of what a program is. Little by little the software is updated and tested in a real time environment. Users will be able to test and improve the software as they are created. This goes in a different pattern if you compare it to the regular SDLC pattern, and the feedback is only in the later stage. If there are any changes, it has to go back to the drawing board, wasting more time. Prototype Models Types There are four types of Prototype Models based on their development planning: the Patch-Up Prototype Nonoperational Prototype First-of-a-Series Prototype Selected Features Prototype.

What is RAD?
The idea of reusing codes and tools is what defines another form of Software Development Life Cycle called Rapid Application Development, or RAD. This form of software development constantly refers to the objective. Instead of creating original coding, developers use other tools such as software development kits and other graphic user interfaces to create programs. RAD also relies heavily on the available codes and reuses it to fit the intended program. Since RAD uses GUI, development kits and existing codes, software development will be faster.

Phases of RAD
1. Planning of Requirements 2. RAD Design Workshop 3. Implementation Phase

System Analyst Roles and Responsibilities


The role of an analyst is to help organizations understand the challenges before them to make this transition and to ensure that the needs and expectations of the client are represented correctly in the final solution. Each company needs to define the specific roles and responsibilities that an analyst plays in their organization.

Process Responsibilities
Once the Analysis Phase begins, the analyst plays a key role in making sure that the overall project successfully meets the client needs. This includes: Analyzing and understanding the current state processes to ensure that the context and implications of change are understood by the clients and the project team Developing an understanding of how present and future business needs will impact the solution Identifying the sources of requirements and understanding how roles help determine the relative validity of requirements Developing a Requirements Management Plan and disseminating the Plan to all stakeholders Identifying and documenting all business, technical, product and process requirements Working with the client to prioritize and rationalize the requirements Helping to define acceptance criteria for completion of the solution

Database Administrator Roles and Responsibilities A Database Administrator, Database Analyst or Database Developer is the person responsible for managing the information within an organization. As most companies continue to experience inevitable growth of their databases, these positions are probably the most solid within the IT industry. Implementation of data models Database design Database accessibility Performance issues Capacity issues Data replication Table Maintenance

Database Designer
The database designer role defines the tables, indexes, views, constraints, triggers, stored procedures, tablespaces or storage parameters, and other database-specific constructs needed to store, retrieve, and delete persistent objects. The database designer must have a solid working knowledge of the following: Database and Object-Oriented Analysis and Design techniques System Architecture, including Database and System performance tuning, as well as hardware and network workload balancing Database Administration an understanding of the implementation language and environment

System Development Life Cycle The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project from an initial feasibility study through maintenance of the completed application.

Computer Aided Software Engineering (CASE) CASE tools reduce the time and cast of software development and ensure the quality of software. The objective of introducing Computer Aided Software Engineering (CASE) tools was the reduction of the time, cost of software development and for the enhancement of the quality of the systems developed.

CASE technologies are tools that provide automated assistance for software development to the developers. The goal of introducing CASE tools is to reduce the time of development, reduce the cost of software, and the enhancement of the quality of the software.

Need of CASE They provides better perceptive of system. Facilitates communication among team members. Tools are more effective for large scale systems and immense projects. CASE tools provide visibility of processes and logic. CASE tools improve quality and productivity of software. CASE tools reduce the time for error correction and maintenance. CASE tools provide clear readability and maintainability of the system.

Modular approach to Software Development In structured design as explained in structured diagram, the system is divided into different modules that are organized in a top down manner. The steps are: Identification of inputs and outputs from SRS Description of functions aspects of the system Representation of system in DFDs Formation of data dictionary Documentation of structure design by structure charts.

Information System Audit Information systems should be periodically examined or audited by good teams may be first by a companys internal auditing staff or external auditors from professional accounting firms or both one following the other. any business, the audit of the business records and documents are conducted periodically or at the end of the year. The auditors study documents like ledgers, balance sheets etc. to see whether the documents have been prepared correctly and the entire lot of transaction have been account properly. In accounting, a financial transaction of the basic entity. In a computer system, a transaction is the smallest entity. A transaction is any event which takes place in an organization like putting a value in a field, adding numbers, printing a report, input value etc.

ENTERPRISE RESOURCE PLANNING


Enterprise: The whole Business venture. Resource of an enterprise: Financial application Human resources Marketing & sales Supply chain management More recently used business function

Enterprise resource planning or ERP consists of three word enterprise, resource and planning. Among the three the last two words are insignificant compared to the first. Yes ERP packages do help in planning and also in managing the resources. There are many other software solutions that does the same thingplanning and resource management.

WHAT IS ERP:Integrates all departments and the functions across organization onto a single system (and database). Facilitates the development of common processes Facilitates agreement on common data ERP systems are a suite of software applications that have revolutionized the way enterprises do business. They support the reengineering of business processes in all areas of activity, including manufacturing, human resources, finance, accounting, and sales. ERP applications automate and integrate business processes across departments and functions They allow information to flow seamlessly from one end of the company to the other and provide a single unified business environment.

FUNCTION AREAS & BUSINESS PROCESSES:Marketing & Sales Marketing of a product Supply chain Management Purchasing goods and raw materials Accounting & Finance Human Resources

Financial accounting of Recruiting and hiring payments from customers and to suppliers Training

Taking sales orders

Receiving goods and raw Cost allocation and materials control

Customer support
Customer relationship management

Transportation and logistics


Scheduling production runs

Planning and budgeting


Cash flow management

Payroll
Benefits

Sales forecasting
Advertising

Manufacturing goods
Plant maintenance

government compliance

Types of ERP structure The two popular types of ERP architecture are: Two-Tier Architecture Three Tier Architecture

Advantages of ERP Systems No data redundancy, which virtually eliminates inconsistencies in data Online data validation, which results in data being relatively error-free Cross-functional integration, which facilitates streamlined and automated procedures that span functional areas Ability to perform cross-functional queries to answer enterprise wide questions Ability to generate real-time reports Ability to drill down to view details of summary reports
Disadvantages of ERP Systems High cost of the software itself, consultants, employee time, and training Requires significant changes in corporate culture and business processes. Complex and extended undertaking that can fail and waste millions of dollars. Extensive reliance on the ERP vendor

Supply Chain Management


Definition A supply chain is the stream of processes of moving goods from the customer order through the raw materials stage, supply, production, and distribution of products to the customer. All organizations have supply chains of varying degrees, depending upon the size of the organization and the type of product manufactured. These networks obtain supplies and components, change these materials into finished products and then distribute them to the customer. Managing the chain of events in this process is what is known as supply chain management.

There are six key elements to a supply chain:


Production Supply Inventory Location Transportation, and Information

S-ar putea să vă placă și