2. How has your answer to question 1 this week changed from your post in response to this same question when it was asked in Week 2?
Yes, it is changed. The answer is changed because in week one I had expressed few things but now I feel, I have clearer picture of the system analyst than before.
3. How well did your actual study for the course this term match the study schedule outlined in the Gantt chart you prepared in week 3?
Yes it matched but only a few delays in few weeks.
4. If you were in charge of this course next term, what changes would you make to improve the course? Why?

System Development Overview basically emphasises on the practical approach of learning System Analysis and Design using a range of traditional development with current technologies. This overview describes the System Development Life Cycle i.e. SDLC, this is divided into 5 phases i.e. Analysis, Planning, Designing, Implementation and lastly the Operation and Support. In addition to this it even explains the Analysis of toolkit which highlights the importance of economic analysis, communication, and project planning skills across the phases of SDLC. It even explains the alternate development methodologies for developing new information system. This helps in understanding of how the IT arena supports operational and business requirements in present cutting-edge world and competitive environment. It gives clear overview of how to solve problems and how the analysts communicate with users, management, other employees and IT professionals in a business organization.

I would have not made any changes as I feel the course is well planned.

1. Why do you think those concepts are important?
These concepts are important because these concepts completely explain a business and its working.
2. What concepts from this course are still causing you the greatest problems?
The greatest problems I feel in this course are the study of a business case and preparing its 0 level DFD table I opt few entities and attributes but I get confused of judging weather it could be more good.
3. How might the problems you are having be solved?
This problem can be solved by reading more concepts of DFD’s

Sl.No. Agile software Traditional software
1. It is combined It is distinct
2. It adopts a adoptive approach It adopts a predictive approach
3. Agile Software is cost effective Traditional software is not cost effective
4. Changes can be made easily to agile software and testing can be done after every few weeks or more. Since the integration and testing is done at the end of the cycle, it would be difficult to change things instantly.
5. Its influence is high short targets. It is effects highly on highly targeted projects
6. External environment cause critical change or differences Assumes that differences result to errors
7. It influence on people, communication, software, customer collaboration change Influences on processes, contracts and plans.
8. It influence on people, communication, software, customer collaboration change Influences on processes, contracts and plans.
9. It is practical It is mechanical
10. The team will not be able to predict the mission state for future. It can report undertaken next week, but cannot predict longer Time An team can report accurately which features and task is planned for the whole development.

1. What were the most important concepts you learnt this week?

Data design conceptsData StructureOverview of File ProcessingOverview of Database SystemsData managementDBMS ConceptsData Manipulation Language Web – Based Data base designPrimary key Candidate key Foreign key Secondary key Entity Relationship Diagrams (ERD)Drawing an ERD Types of RelationshipsOne to One relationshipOne to Many relationshipMany to Many relationshipCardinality Notation 

1. Why do you think those concepts are important?

These concepts are important because these concepts completely explain a business and its working.

1. What concepts from this week are causing you the greatest problems?

Cardinality Notation is the greatest problem I face in this week concepts. 

1. How might the problems you are having be solved?

This problem can be solved by practicing these notations. 

]]> http://s0096797.wordpress.com/2006/08/04/10/feed/ 0 raj http://s0096797.wordpress.com/2006/08/04/9/ http://s0096797.wordpress.com/2006/08/04/9/#comments Fri, 04 Aug 2006 07:04:41 +0000 s0096797 https://s0096797.wordpress.com/2006/08/04/9/ ]]> THE GANTT CHART FOR TERM 1 

]]> http://s0096797.wordpress.com/2006/08/04/9/feed/ 0 raj http://s0096797.wordpress.com/2006/08/03/7/ http://s0096797.wordpress.com/2006/08/03/7/#comments Thu, 03 Aug 2006 07:56:38 +0000 s0096797 https://s0096797.wordpress.com/2006/08/03/7/ ]]> ]]> http://s0096797.wordpress.com/2006/08/03/7/feed/ 0 raj http://s0096797.wordpress.com/2006/07/26/skills/ http://s0096797.wordpress.com/2006/07/26/skills/#comments Wed, 26 Jul 2006 10:24:27 +0000 s0096797 https://s0096797.wordpress.com/2006/07/26/skills/ ]]> Week 2: SYSTEM DEVELOPMENT OVERVIEW

1) What are the skills and knowledge that a good systems analyst requires?        

All organizations rely on computer and information technology to conduct business and operate more efficiently. The rapid spread of technology across all industries has generated a need for highly trained workers to help organizations incorporate new technologies. The tasks performed by workers known as computer Systems Analysts. System analyst evolves rapidly, reflecting new areas of specialization or changes in technology, as well as the preferences and practices of employers.

Computer systems analysts solve computer problems and apply computer technology to meet the individual needs of an organization. They help an organization to realize the maximum benefit from its investment in equipment, personnel, and business processes. Systems analysts may plan and develop new computer systems or devise ways to apply existing systems’ resources to additional operations. They may design new systems, including both hardware and software, or add a new software application to harness more of the computer’s power. Most systems analysts work with specific types of systems—for example, business, accounting, or financial systems, or scientific and engineering systems—that vary with the kind of organization. Some systems analysts also are known as systems developers or systems architects.

Systems analysts begin an assignment by discussing the systems problem with managers and users to determine its exact nature. Defining the goals of the system and dividing the solutions into individual steps and separate procedures, systems analysts use techniques such as structured analysis, data modeling, information engineering, mathematical model building, sampling, and cost accounting to plan the system. They specify the inputs to be accessed by the system, design the processing steps, and format the output to meet users’ needs. They also may prepare cost-benefit and return-on-investment analyses to help management decide whether implementing the proposed technology will be financially feasible.

When a system is accepted, systems analysts determine what computer hardware and software will be needed to set the system up. They coordinate tests and observe the initial use of the system to ensure that it performs as planned. They prepare specifications, flow charts, and process diagrams for computer programmers to follow; then, they work with programmers to “debug,” or eliminate, errors from the system. Systems analysts who do more in-depth testing of products may be referred to as software quality assurance analysts. In addition to running tests, these individuals diagnose problems, recommend solutions, and determine whether program requirements have been met.

In some organizations, programmer-analysts design and update the software that runs a computer. Because they are responsible for both programming and systems analysis, these workers must be proficient in both areas. (A separate statement on computer programmers appears elsewhere in the Handbook.) As this dual proficiency becomes more commonplace, these analysts are increasingly working with databases, object-oriented programming languages, as well as client–server applications development and multimedia and Internet technology.

One obstacle associated with expanding computer use is the need for different computer systems to communicate with each other. Because of the importance of maintaining up-to-date information—accounting records, sales figures, or budget projections, for example—systems analysts work on making the computer systems within an organization, or among organizations, compatible so that information can be shared among them. Many systems analysts are involved with “networking,” connecting all the computers internally—in an individual office, department, or establishment—or externally, because many organizations rely on e-mail or the Internet. A primary goal of networking is to allow users to retrieve data from a mainframe computer or a server and use it on their desktop computer. Systems analysts must design the hardware and software to allow the free exchange of data, custom applications, and the computer power to process it all. For example, analysts are called upon to ensure the compatibility of computing systems between and among businesses to facilitate electronic commerce.

System Analyst Assists users in developing database application requirements and determines if needs can be met with existing, commercial software or would need custom programming.

Collaboratively develops, maintains, and tests new and enhanced networked and stand-alone applications using a database programming language.

Provides technical assistance and documentation to end-users.

Writes and maintains technical documentation for all applications.

Provides end-user support for the Association Management System (AMS), including requests for advanced database queries and reports.

Converts data and creates data integration interfaces and DTS packages.

How do you plan to develop those skills?

Attainment Levels

Application Design

Define basic terminology

Document the sequence in which processing is performed and how data is passed between processes.

Develop program design specifications

Design and document logical databases, program modules, describing purpose and

Programming 

Identify and describe programming concepts

Explain programming standards

Apply programming standards

Translate technical design specifications into concise code

Apply programming concepts, coding in at least two programming languages and at least one

Data Management

Explain data design terms relevant to this domain

Explain the difference between conceptual, logical and physical design

Explain the differences between network, relational and hierarchical and other relevant data models

Design and develop relational data models

Use normalization techniques

Use Data Modeling

Platform Management

Define generic systems architecture components such as hardware, physical network, system software and infrastructure

Perform resolution of hardware problems, including configuration errors and equipment failures

Perform configuration of a complete workstation or server

Analyze workstation or server storage, CPU and memory resources for performance and adequacy on an ongoing basis and perform system tuning

Networking

 Define basic networking terms such as LAN, WAN, Internet/intranet/extranet, networking protocols, directory services

Describe the logical and physical layout of networks

Analyze and diagnose hardware, communications and application problems

Perform configuration/reconfiguration and maintenance of various network and communications

hardware (e.g. servers, routers, controllers) using available resources (manuals, instructions, etc.)

 Perform communications and network support for clients

Perform planning, installation and maintenance of both a peer-to-peer and a server based network

Perform planning and installation of an Internet connection for a local area network

Solutions Implementation

 Identify and describe basic testing, acceptance and conversion concepts and terminology

 Use installation strategies

 Develop and perform test plans, acceptance testing and conversion plans

 Verify accuracy, acceptability and integrity of implementation

 Develop and use corrective measures

 Develop and apply deployment strategies

Technical Security Management

Define key generic security concepts such as authentication, authorization and public key

Infrastructure

List the key characteristics of a disaster recovery plan

Explain the threats posed by the computer virus and other malicious code and identify prevention measures.

Explain the various security strategies

Discuss the security strategies applied to applications and their suitability and limitations for different business purposes

Apply appropriate security strategies in applications

Use methods of maintaining current awareness of virus and security issues and exploits, and prevention and countermeasure Perform security management Perform communication of security practices

Operating Systems

 Identify and list the characteristics of operating systems Perform installation, configuration and management of at least one desktop operating system Generic IT Career Elements

Customer/Client Contact/Service

 Explain the importance of common ethical policies and procedures and relate policies and procedures to clients

Demonstrate accuracy and courtesy in responses to customer inquiries, questions or requests

 Identify/adapt/integrate with customer and corporate culture where appropriate

 Demonstrate customer relationship skills

 Demonstrate customer follow-up skills

Communication

Perform writing of business communications (letters, memos, e-mail, business reports)

Use technical communications (flowcharts, diagrams, specifications, and diagnostics)

Use projectors, graphics and multimedia in making presentations

Use Oral Communications (listening, interviewing, speaking, and telephone/teleconferencing)

Demonstrate professional conduct in communications

Demonstrate understanding of individual’s roles and responsibilities as part of a team

Demonstrate the ability to work in partnership with technical and non-technical counterparts

Demonstrate the ability to participate in-group work towards common goals (deadlines, budgets, and workload distribution)

Demonstrate openness and integration of different points of view
Independence

Demonstrate responsibility for one’s own work   

Perform work independently with minimal supervision

Develop work ethics and provide continuous learning

Personal Productivity / Organizational Skills

List concepts of personal time management

Demonstrate acceptable time management skills and use time management tools to meet deadlines, be on time, etc.

 Understand and use filing systems (e.g. central filing)

Project Management

Use tools of project management in a major assignment to:

· Develop estimates for key activities

· Plan work in terms of time, budget and resources required (set targets, plan simple projects)

· Monitor progress against plan

· Adjust course of action as plan is implemented

· Manage change

· Report on progress

Problem Solving and Decision Making

 Follow a problem solving methodology that:

· Documents the problem

· Generates alternatives to solving the problem

· Develops decision making criteria

· Evaluates the alternatives

· Recommends the preferred course of action

· Prepares appropriate documentation at all points in the decision making process