Sunday, February 14, 2010

Michael Learns To Rock - It's Gonna Make Sense lyrics


It's gonna make sense

Ah... ah... ah...
Ah... ah... ah... ah...

Life comes in many shapes
You think you know what you got
Until it changes

And life will take you high and low
You gotta learn how to walk
And then which way to go

Every choice you make
When you're lost
Every step you take
Has it's cause

Chorus:
After you clear your eyes
You'll see the light
Somewhere in the darkness
After the rain has gone
You'll feel the sun come
And though it seems your sorrow never ends
Someday it's gonna make sense

Ah... ah... ah... ah...

Tears you she'd are all the same
When you laughed 'till you cried
Or broken down in pain

All the hours you have spent in the past
Worrying about
A thing that didn't last

Everything you saw
Played a part
In everything you are
In your heart

Chorus:
After you clear your eyes
You'll see the light
Somewhere in the darkness
After the rain has gone
You'll feel the sun comes
And though it seems your sorrow never ends...

Release:
Someday you're gonna find the answers
To all the things you've become and all they've done
At your expense
Someday it's gonna make sense

Ah... ah... ah...
Ah... ah... ah... ah...

After the rain has gone
You'll feel the sun comes
And though it seems your sorrow never ends

Someday it's gonna make sense
Ah... ah... ah... ah... ah... ah... ah...
Someday it's gonna make sense

After the rain has gone
You'll feel the sun comes
And though it seems your sorrow never ends

Someday it's gonna make sense

Tuesday, September 22, 2009

Friday, September 4, 2009

i'm dreaming to be a...

Systems analyst

From Wikipedia, the free encyclopedia


A systems analyst is responsible for researching, planning, coordinating and recommending software and system choices to meet an organization's business requirements. The systems analyst plays a vital role in the systems development process. A successful systems analyst must acquire four skills: analytical, technical, managerial, and interpersonal. Analytical skills enable systems analysts to understand the organization and its functions, which helps him/her to identify opportunities and to analyze and solve problems. Technical skills help systems analysts understand the potential and the limitations of information technology. The systems analyst must be able to work with various programming languages, operating systems, and computer hardware platforms. Management skills help systems analysts manage projects, resources, risk, and change. Interpersonal skills help systems analysts work with end users as well as with analysts, programmers, and other systems professionals.

Because they must write user requests into technical specifications, the systems analysts are the liaisons between vendors and the IT professionals of the organization they represent They may be responsible for developing cost analysis, design considerations, and implementation time-lines. They may also be responsible for feasibility studies of a computer system before making recommendations to senior management.

Basically, a systems analyst performs the following tasks:

  • Interact with the customers to know their requirements
  • Interact with designers to convey the possible interface of the software
  • Interact/guide the coders/developers to keep track of system development
  • Perform system testing with sample/live data with the help of testers
  • Implement the new system
  • Prepare High quality Documentation

Tuesday, September 1, 2009

Data Flow Diagram


Data flow diagram
From Wikipedia, the free encyclopedia


Data Flow Diagram example.[1]A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. DFDs can also be used for the visualization of data processing (structured design).

On a DFD, data items flow from an external data source or an internal data store to an internal data store or an external data sink, via an internal process.

A DFD provides no information about the timing or ordering of processes, or about whether processes will operate in sequence or in parallel. It is therefore quite different from a flowchart, which shows the flow of control through an algorithm, allowing a reader to determine what operations will be performed, in what order, and under what circumstances, but not what kinds of data will be input to and output from the system, nor where the data will come from and go to, nor where the data will be stored (all of which are shown on a DFD).






Overview

It is common practice to draw a context-level data flow diagram first, which shows the interaction between the system and external agents which act as data sources and data sinks. On the context diagram (also known as the Level 0 DFD) the system's interactions with the outside world are modelled purely in terms of data flows across the system boundary. The context diagram shows the entire system as a single process, and gives no clues as to its internal organization.

This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the detail of the system being modeled. The Level 1 DFD shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the system as a whole. It also identifies internal data stores that must be present in order for the system to do its job, and shows the flow of data between the various parts of the system.


Data-flow diagrams were invented by Larry Constantine, the original developer of structured design, based on Martin and Estrin's "data-flow graph" model of computation.

Data-flow diagrams (DFDs) are one of the three essential perspectives of the structured-systems analysis and design method SSADM. The sponsor of a project and the end users will need to be briefed and consulted throughout all stages of a system's evolution. With a data-flow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented. The old system's dataflow diagrams can be drawn up and compared with the new system's data-flow diagrams to draw comparisons to implement a more efficient system. Data-flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to report. How any system is developed can be determined through a data-flow diagram.

In the course of developing a set of levelled data-flow diagrams the analyst/designers is forced to address how the system may be decomposed into component sub-systems, and to identify the transaction data in the data model.

There are different notations to draw data-flow diagrams, defining different visual representations for processes, data stores, data flow, and external entities.


Developing a data-flow diagram

data-flow diagram example
data-flow diagram - Yourdon/DeMarco notation
[edit] Top-Down Approach
The system designer makes "a context level DFD" or Level 0, which shows the "interaction" (data flows) between "the system" (represented by one process) and "the system environment" (represented by terminators).
The system is "decomposed in lower-level DFD (Level 1)" into a set of "processes, data stores, and the data flows between these processes and data stores".
Each process is then decomposed into an "even-lower-level diagram containing its subprocesses".
This approach "then continues on the subsequent subprocesses", until a necessary and sufficient level of detail is reached which is called the primitive process (aka chewable in one bite).
DFD is also a virtually designable diagram that technically or diagrammatically describes the inflow and outflow of data or information that is provided by the external entity.


Event Partitioning Approach
Event partitioning was described by Edward Yourdon in Just Enough Structured Analysis.


A context level Data flow diagram created using Select SSADM.
This level shows the overall context of the system and its operating environment and shows the whole system as just one process. It does not usually show data stores, unless they are "owned" by external systems, e.g. are accessed by but not maintained by this system, however, these are often shown as external entities.


Level 1 (High Level Diagram)

A Level 1 Data flow diagram for the same system.
This level (level 1) shows all processes at the first level of numbering, data stores, external entities and the data flows between them. The purpose of this level is to show the major high-level processes of the system and their interrelation. A process model will have one, and only one, level-1 diagram. A level-1 diagram must be balanced with its parent context level diagram, i.e. there must be the same external entities and the same data flows, these can be broken down to more detail in the level 1, e.g. the "inquiry" data flow could be split into "inquiry request" and "inquiry results" and still be valid.


Level 2 (Low Level Diagram)

A Level 2 Data flow diagram showing the "Process Enquiry" process for the same system.
This level is a decomposition of a process shown in a level-1 diagram, as such there should be a level-2 diagram for each and every process shown in a level-1 diagram. In this example processes 1.1, 1.2 & 1.3 are all children of process 1, together they wholly and completely describe process 1, and combined must perform the full capacity of this parent process. As before, a level-2 diagram must be balanced with its parent level-1 diagram.

Wednesday, July 22, 2009


System analysis is the branch of electrical engineering that characterizes electrical systems and their properties. Although many of the methods of system analysis can be applied to non-electrical systems, it is a subject often studied by electrical engineers because it has direct relevance to many other areas of their discipline, most notably signal processing and communication systems.
Introduction to System Analysis and Design

Introduction to System Analysis and Design

INTRODUCTION

Systems are created to solve problems. One can think of the systems approach as an organized way of dealing with a problem. In this dynamic world, The subject System Analysis and Design, mainly deals with the software development activities.

OBJECTIVES

After going through this lesson, you should be able to:

  • understand a system
  • understand the different phases of system developments life cycle
  • know the components of system analysis
  • know the components of system designing

Defining A System

A collection of components that work together to realize some objective forms a system. Basically there are three major components in every system, namely input, processing and output.

In a system the different components are connected with each other and they are interdependent. For example, Human body represents a complete natural system. We are also bound by many national systems such as political system, economic system, educational system and so forth. The objective of the system demand that some output is produced as a result of processing the suitable inputs.

SYSTEM LIFE CYCLE

System life cycle is an organisational process of developing and maintaining systems. It helps in establishing a system project plan, because it gives overall list of processes and sub-processes required developing a system.

System development life cycle means combination of various activities. In other words we can say that various activities put together are referred as system development life cycle. In the System Analysis and Design terminology, the system development life cycle means software development life cycle.

Following are the different phases of software development cycle:

  • System study
  • Feasibility study
  • System analysis
  • System design
  • Coding
  • Testing
  • Implementation
  • Maintenance

The different phases of software development life cycle is shown in Fig.29.1

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

Let us now describe the different phases and the related activities of system development life cycle in detail.

System Study

System study is the first stage of system development life cycle. This gives a clear picture of what actually the physical system is? In practice, the system study is done in two phases. In the first phase, the preliminary survey of the system is done which helps in identifying the scope of the system. The second phase of the system study is more detailed and in-depth study in which the identification of user’s requirement and the limitations and problems of the present system are studied. After completing the system study, a system proposal is prepared by the System Analyst (who studies the system) and placed before the user. The proposed system contains the findings of the present system and recommendations to overcome the limitations and problems of the present system in the light of the user’s requirements.

To describe the system study phase more analytically, we would say that system study phase passes through the following steps:

  • problem identification and project initiation
  • background analysis
  • inference or findings

Feasibility Study

On the basis of result of the initial study, feasibility study takes place. The feasibility study is basically the test of the proposed system in the light of its workability, meeting user’s requirements, effective use of resources and .of course, the cost effectiveness. The main goal of feasibility study is not to solve the problem but to achieve the scope. In the process of feasibility study, the cost and benefits are estimated with greater accuracy.

System Analysis

Assuming that a new system is to be developed, the next phase is system analysis. Analysis involved a detailed study of the current system, leading to specifications of a new system. Analysis is a detailed study of various operations performed by a system and their relationships within and outside the system. During analysis, data are collected on the available files, decision points and transactions handled by the present system. Interviews, on-site observation and questionnaire are the tools used for system analysis. Using the following steps it becomes easy to draw the exact boundary of the new system under consideration:

  • Keeping in view the problems and new requirements
  • Workout the pros and cons including new areas of the system

All procedures, requirements must be analysed and documented in the form of detailed data flow diagrams (DFDs), data dictionary, logical data structures and miniature specifications. System Analysis also includes sub-dividing of complex process involving the entire system, identification of data store and manual processes.

The main points to be discussed in system analysis are:

  • Specification of what the new system is to accomplish based on the user requirements.
  • Functional hierarchy showing the functions to be performed by the new system and their relationship with each other.
  • Function network which are similar to function hierarchy but they highlight the those functions which are common to more than one procedure.
  • List of attributes of the entities - these are the data items which need to be held about each entity (record)

System Design

Based on the user requirements and the detailed analysis of a new system, the new system must be designed. This is the phase of system designing. It is a most crucial phase in the development of a system. Normally, the design proceeds in two stages :

  • preliminary or general design
  • Structure or detailed design

Preliminary or general design: In the preliminary or general design, the features of the new system are specified. The costs of implementing these features and the benefits to be derived are estimated. If the project is still considered to be feasible, we move to the detailed design stage.

Structure or Detailed design: In the detailed design stage, computer oriented work begins in earnest. At this stage, the design of the system becomes more structured. Structure design is a blue print of a computer system solution to a given problem having the same components and inter-relationship among the same components as the original problem. Input, output and processing specifications are drawn up in detail. In the design stage, the programming language and the platform in which the new system will run are also decided.

There are several tools and techniques used for designing. These tools and techniques are:

  • Flowchart
  • Data flow diagram (DFDs)
  • Data dictionary
  • Structured English
  • Decision table
  • Decision tree

Each of the above tools for designing will be discussed in detailed in the next lesson.

Coding

After designing the new system, the whole system is required to be converted into computer understanding language. Coding the new system into computer programming language does this. It is an important stage where the defined procedure are transformed into control specifications by the help of a computer language. This is also called the programming phase in which the programmer converts the program specifications into computer instructions, which we refer as programs. The programs coordinate the data movements and control the entire process in a system.

It is generally felt that the programs must be modular in nature. This helps in fast development, maintenance and future change, if required.

Testing

Before actually implementing the new system into operations, a test run of the system is done removing all the bugs, if any. It is an important phase of a successful system. After codifying the whole programs of the system, a test plan should be developed and run on a given set of test data. The output of the test run should match the expected results.

Using the test data following test run are carried out:

  • Unit test
  • System test

Unit test: When the programs have been coded and compiled and brought to working conditions, they must be individually tested with the prepared test data. Any undesirable happening must be noted and debugged (error corrections).

System Test: After carrying out the unit test for each of the programs of the system and when errors are removed, then system test is done. At this stage the test is done on actual data. The complete system is executed on the actual data. At each stage of the execution, the results or output of the system is analysed. During the result analysis, it may be found that the outputs are not matching the expected out of the system. In such case, the errors in the particular programs are identified and are fixed and further tested for the expected output.

When it is ensured that the system is running error-free, the users are called with their own actual data so that the system could be shown running as per their requirements.

Implementation

After having the user acceptance of the new system developed, the implementation phase begins. Implementation is the stage of a project during which theory is turned into practice. During this phase, all the programs of the system are loaded onto the user's computer. After loading the system, training of the users starts. Main topics of such type of training are:

  • How to execute the package
  • How to enter the data
  • How to process the data (processing details)
  • How to take out the reports

After the users are trained about the computerised system, manual working has to shift from manual to computerised working. The following two strategies are followed for running the system:

  1. Parallel run: In such run for a certain defined period, both the systems i.e. computerised and manual are executed in parallel. This strategy is helpful because of the following:
    • Manual results can be compared with the results of the computerised system.
    • Failure of the computerised system at the early stage, does not affect the working of the organisation, because the manual system continues to work, as it used to do.
  1. Pilot run: In this type of run, the new system is installed in parts. Some part of the new system is installed first and executed successfully for considerable time period. When the results are found satisfactory then only other parts are implemented. This strategy builds the confidence and the errors are traced easily.

Maintenance

Maintenance is necessary to eliminate errors in the system during its working life and to tune the system to any variations in its working environment. It has been seen that there are always some errors found in the system that must be noted and corrected. It also means the review of the system from time to time. The review of the system is done for:

  • knowing the full capabilities of the system
  • knowing the required changes or the additional requirements
  • studying the performance

If a major change to a system is needed, a new project may have to be set up to carry out the change. The new project will then proceed through all the above life cycle phases.

AN ARTICLE FROm google.com