week12

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

Ans. 1: A good system analyst have good capability about the way of investigation, analyses and designs, develops, installs, evaluates and maintain a company’s information systems. A good analyst always keeps in touch with users and his managers and outside of any company’s managers. System analyst always keen his eyes toward the analyze of a critical situation for the company. He should have strong knowledge, oral and written communication skills. When systems analyst making a career decision of any company, he must enables the to consider salary, location and future growth   potential.

 

 

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?

 

Ans. 2: At the begging of this course, I don’t have enough knowledge about which type of responsibilities and knowledge system analyst should require? I also had less idea about the importance of system analysis and design part. But as the last stage of course I realized that system analysis and designs presents a practical approach to information technology and systems developments. I also realized that without system analyst, business organization can not emphasize the critical-thinking skills.

 

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?

 

 

Ans. 3: The Gantt chart is a one type of schedule that provides step by step planning to complete your project. So I follow this subject as per my Gantt chat planning. But at time of week 9 and 10 i could not able to read some the chapter according to Gantt chart planning.

 

4. If you were in charge of this course next term, what changes would you makes to improve the course? Why?

 

Ans.4: If I was taking in charge of   this course, I would try to search more topics deeply like practical example of how to company make system analysis and designs for particular business organization. So I can take more idea for this subject? I would check weekly assignment on weekly. So I could solve the student’s problem.

 

 

 

 

week11

Que1: What were the most important concepts you learnt from this course?  Ans1 : During This course we learnt about the overview of information system, system development life cycle and role of system analysis and design in supporting business objectives. We learnt analyzing the business case that that include feasibility, review of system request, requirement of modeling.We also learn important part of SDLC, the Data and Process Modeling techniques to develop a logical model and physical model of the process. When we try to make new system, we need first gather information in logical way and then represent in graphical diagram. This model called Logical Model. Then learnt about the output and user interface design which should highlight output, report design and the interaction between humans and computers.Well after this we learnt Data design terms, concept and skills entity-relationship diagrams, cardinality, data normalization, rules, data ware house, their mining. After this we learnt System architecture’s issue and topics, different type of changeover method for change system and post-implementation evaluation.So although we learnt how should design a computer based new system accurately, r implication, updation.  

Que2: Why do you think those concepts are important?

Ans2: This concept is very important because from this we know the information technolgy’system and development. We would make a good system analyst that emphasizes the role of the system analyst in a dynamic, business-related environment.We learnt how to translate business requirements into information system that support a company’s shout and long-term objectives.Thos concepts give the knowledge of analytical terms, problem-solving and decision-making techinques.These concepts gives emphasize of the development of critical-thinking skills. 

Que3:What concepts from this course are still causing you the greatest problems? Ans 3 : During this course  ,I have problem in cardinality concept and normalization. I can not understand about candidate key and super key that how where, when can I used? I have made mistake when implementing the DFD, ERD and probably define candidate key. 4. How might the problems you are having be solved?Ans 4 : I must refer  books of system analysis. By searching internet and my university library I will take more knowledge about my problem. Regarding my problem I will also need to take staffs help.

week11

 

Que1: What were the most important concepts you learnt from this course?  Ans1 : During This course we learnt about the overview of information system, system development life cycle and role of system analysis and design in supporting business objectives. We learnt analyzing the business case that that include feasibility, review of system request, requirement of modeling.We also learn important part of SDLC, the Data and Process Modeling techniques to develop a logical model and physical model of the process. When we try to make new system, we need first gather information in logical way and then represent in graphical diagram. This model called Logical Model. Then learnt about the output and user interface design which should highlight output, report design and the interaction between humans and computers.Well after this we learnt Data design terms, concept and skills entity-relationship diagrams, cardinality, data normalization, rules, data ware house, their mining. After this we learnt System architecture’s issue and topics, different type of changeover method for change system and post-implementation evaluation.So although we learnt how should design a computer based new system accurately, r implication, updation.  

 

Que2: Why do you think those concepts are important? Ans2: This concept is very important because from this we know the information technolgy’system and development. We would make a good system analyst that emphasizes the role of the system analyst in a dynamic, business-related environment.We learnt how to translate business requirements into information system that support a company’s shout and long-term objectives.Thos concepts give the knowledge of analytical terms, problem-solving and decision-making techinques.These concepts gives emphasize of the development of critical-thinking skills. 

 

 

Que3:What concepts from this course are still causing you the greatest problems? Ans 3 : During this course  ,I have problem in cardinality concept and normalization. I can not understand about candidate key and super key that how where, when can I used? I have made mistake when implementing the DFD, ERD and probably define candidate key. 

4. How might the problems you are having be solved?Ans 4 : I must refer  books of system analysis. By searching internet and my university library I will take more knowledge about my problem. Regarding my problem I will also need to take staffs help.

week10

To make longest system is always becomes increasingly difficult to add new features to the system, testing and debugging is impossible to schedule. The traditional development system takes original movement to try to change by imposes a disciplined process upon software development with the aim of making software development more predictable and more efficient. These methodologies have been around for a long time, some time un- successful, bureaucratic, and very stuff to do to follow the methodology that the whole pace of development slows down. While agile methodologies developed as a reaction to the bureaucracy of the traditional methodologies. These new methods attempt a useful compromise between no process and too much process, providing just enough process to gain a reasonable payoff. The most immediate difference is that they are less document-oriented, usually emphasizing a smaller amount of documentation for a given task.The most two different of both systems have following:-v      Agile methods are adaptive rather than predictive:-

• Traditional methods tend to try to plan out a large part of the software process in great detail for a long span of time, this works well until things change. So their nature is to resist change.
• The agile methods, however, welcome change. They try to be processes that adapt and thrive on change, even to the point of changing themselves.
• In an adaptive process the customer has much finer-grained control over the software development process. At every iteration they get both to check progress and to alter the direction of the software development. This leads to much closer relationship with the software developers, a true business partnership

v      Agile methods are people-oriented rather than process-oriented: -

• The goal of Traditional methods is to define a process that will work well whoever happens to be using it.

• Agile methods assert that no process will ever make up the skill of the development team, so the role of a process is to support the development team in their work.

v     In an agile project there is a constant reworking of   the plan with every iteration.

v     Agile development needs small team size and creative. So it is less expansive and for traditional team size is large so might sometimes expansive.

WEEK8

                                                BIBILOGRAPHY 

Reference 1:

Wikipedia, http://en.wikipedia.org/wiki/agile_software_development, [Accessed: 7sept 2006]

Agile method can be working by a sophisticated system analysis procedure as the primary measure of progress. It produces very little system development process into sophisticated stages that must be completed sequentially with very formal division of customer ratification as per their requirement. This software working very fast and simple manner. This software have special team at time change some requirements. It is very suitable for complexities solving problem even at the end of the process.

 Reference 2:

 Truex, D, Baskeville, R & Klein H 1999, Growing Systems in emergent organizations, communications of the ACM, August, vol.42(8), pp. 117-123.

 Agile software system is used for building large complex system that support formal requirements analysis, predefined, specifications and right controls over the system building process. This software development method is basically very time-consuming and experiments system rapidly. This development includes SDLC and iterative so that the process of build system can be repeated over and over again and capable actively promotes system design change by the adopting methods. This software supports predictive methods which useful for any future planning. Thus this software development built experimental system quickly and inexpensively for demonstration and evaluation so that users can better determine information requirements.

 Reference 3:

 Highsmith, J & Cockburn, AC 2001, Agile software development: the business of innovation, computer, sept., vol.34(9), pp.120-127.

 Emergent software development means developing software very rapidly and in short time period. This technology useful for reengineered, change the global markets and quality oriented organization for reduce risk in the competitive markets. This system’s main goals are always considered analysis, dynamic requirements solution, incomplete and usefully complex specification, dynamically changeable. This can be made possible by agile software method.

WEEK 7

                                             WEEK 7ANS.1:This week we learnt about the System design phase of the SDLC. We learnt how we the different data of events useful for the information system.We learnt ERD (Entity Relationship Diagram):It is graphical representation of all systems entities and the relationship among the entities for different events. The ERD based on entity, relationship and attributes. Here the Entity is something about which “the business” went to store data. For example we take person, place, thing or some events so data is collected and Maintained. Entities can be thought of (roughly) as nouns. A data entity is anything real or abstract about which we want to store data. Entity types fall into five classes: roles, events, locations, tangible things or concepts. E.g. employee, payment, campus, book. Specific examples of an entity are called instances. E.g. the employee John Jones, Mary Smith’s payment, etc.  Generally entity has three parts (1)   Strong Entity: Strong Entity:- It is  a database entity that can be uniquely identified by its own attributes alone. Strong Entity does protect the referent object from collection by the entity.(2) Weak Entity: – A Weak Entity is a database entity that cannot be uniquely       identified by its own attributes alone. A weak entity that does not protect the referent object from collection by the garbage collector.(2)   Associative: It is used to solve the problem of two entities with a many-to-many relationshipAttributes are Properties of the entity. It is not global and depends on entity name like property, data element, field. E.g. Name, address, Employee Number, pay rate are all attributes of the entity employee. An attribute or combination of attributes that uniquely identifies one and only one instance of an entity is called a primary key or identifier. E.g. Employee Number is a primary key for EmployeeAttributes in an ER model may be further described as multi-valued, composite, or derived. A multi-valued attribute, illustrated with a double-line ellipse, may have more than one value for at least one instance of its entity. For example, a piece of software (entity=application) may have the multivalued attribute “platform” because at least one instance of that entity runs on more than one operating system. A composite attribute may itself contain two or more attributes and is indicated as having at least contributing attributes of its own. For example, addresses usually are composite attributes, composed of attributes such as street address, city, and so forth.A Derived attributes are attributes whose value is entirely dependent on another attribute and are indicated by dashed ellipses. For example, if we have an employee database with an employee entity along with an age attribute, the age attribute would be derived from a birth date attribute. Relationship: - A relationship captures how two or more entities are related to one another. Relationships can be thought of (again, roughly) as Verbs Examples: an owns relation between a company and a computer, a supervises relation between an employee and a department, a performs relation between an artist and a song, a proved relation between a mathematician and a theorem. Entities are drawn as rectangles, relationships as diamonds.Types of Relationships: – (1)  A one-to-one relationship exists when exactly one of the second entities occurs for each instance of the first entity.(2)  A one-to-many relationship exists when one occurrence of the first entity can relate to many instances of the second entity, but each instance of the second entity can associate with only one instance of the first entity.(3)  A many-to-many relationship exists when one instance of the first entity can relate to many instances of the second entity and of instances of the second entity can relate to many instances of the first entity. Cardinality:-It will describes the numeric relationship between two entities and shows how instances of one entity relate to instances of another entity. System Analyst use cardinality notation, which uses special symbols to represent the relationship.ANS.2: -          In Information System an entity-relationship model is a model providing a high-level description of a conceptual date mode conceptual data model. Which is a map of concepts and their relationships. System analyst make graphical notation for representing such data models, including entities, common fields, records, files, tables, and key fields in the form of entity-relationship diagram (ERD). The most important use of ERD is represent user-approved model of the new system and it would identify all systems entities and the relationships among them. It would be better to design the basic system first and then address other issues including web enhancements and implementation option, timeless method, cost-effective, accomplish a specific set of functions, technically sounds and also useful to updating and maintains for developing project. Thus process has proved to enable the analyst to produce a good database structure so that the data can be stored and retrieved in a most efficient manner. 

ANS.3: - If System Analyst does not have proper knowledge about how to top-to-bottom and left-to-right fashion for making ERD then it will make causing for particular Information System. In an ERD, relationships and cardinality notation are not mention very well then it will create big problem to developing system. If primary key, candidate key are not properly mention then also create big problem for data manipulation.

ANS.4: -System analyst might build ERD in top-to-bottom and left-to-right fashion. They must ask face-to-face communication for user requirement and satisfaction before making module and after making module. Like(1)   Identify the roles, events, and concepts as per user requirement to store data in entities.(2)   Find the natural association between pairs of entities.(3)   Draw Rough ERD and Fill in Cardinality for determine the number of occurrences of one entity to another entity.(4)   Define various identifiers for identify the data attributes.

(5)    Identify Attributes and Map Attributes.

(6) Finally Check Results.

Week 6

Out put and user interface design:- Output and user interface design is the first task in the systems design phase of the the SDLC. *Output is need to printed reports, displayed various reports on screen as per User requirements.>Generally system designee needs reports, screen forms, and following output types:(1) Internet-Based Information Delivery:These are very useful to guide E-commerce or web designing part for attracting and making user friendly screen interface.(2) E-mail:-It is very fast and good accessible for external and internal communication within few second.(3) Audio:-These facilities send by attaching email message or Microsoft document.(4)Automated Facsimile System:-This is Fax-back system. We send it by email or telephone.(5)Computer Output Microfilmed.(6)Computer Output to Laser Disk. We also learned estimate printing volume and time. Also we learned output control to make our information complete, secure and correct. 

*User interface design stresses user interaction with the computer, including input design a procedure. It is like Graphical user interface designed that interacts with system and included of all the system integral parts like hardware, software, menus functions. We learned human-computer interaction concepts and GUI that is useful to user for communicate system by allowing graphical object and techniques.We also learned basic principal of user – cenntered design and guideline for user interfaces. We learned interface design guidelines for understanding on basic objectives, make easy to learn, use, efficiency, minimizine input data, correct errors, provide feedback to users, use familiar terms and images. We also learned various control like menu bars, toolbars, drop-down list boxes etc to place on main switch board. 

The above topic of out put and user interface is used in My CQU website.This website can include everything like cqu library, student and staff related Information. All information are consist very graphically and user can fetch information with easily understanding. This website use user-friendly tools.  This web site access by authentication like provide username, password for preventing unauthorized user.

WEEK-4 ASSIGNEMENT

ANS1:The Data and Process Modelling techniques to develop a logical model and physical model of the process. When we try to make new system, we need first gather information in logical way and then represent in graphical diagram. This model called Logical Model. 

A set of DFD (Data Flow of Diagram) provides a logical model that shows what system does, not how it does. DFD have three content. (1)Data Model, (2) Process Model, (3) User Interface. 

* DFD Symbol: – It has four symbols for processes, data flows, data stores and entities, exit. DFD Symbol set uses two ways (1) According to Gane and Sarson symbol set and (2) According to Yourdon Symbol set. The most software company apply Gane and sarson symbol to make DFD.*Process Symbol: –

• It symbol represent as rectangle and referred to as black box because we know inputs, outputs and general function of the process but logical part are hidden.
• It is receives input data and produces output that has different content. In typical design like company we need online resource for fetch and sending on word wide .That time we require business logic or business rule which   transform the data and produce the output regarding the requirement.

*Data Flow Symbol:·  

      This is data’s path for moving information from one direction to another direction.

       It can be represent one or more data items.·   

    DFD could not contain following Data flow error.

(1)   Spontaneous generation/Miracle: – If there is not input data flow called Miracle process.

(2)   Black Hole: – If process has input but not output than called Black Hole.

(3)   Gray Hole: – It has one input and one output but if output has no sufficient information than called Gray Hole. 

*Data Store Symbol:-·

 It is used in a DFD to represent data that the system stores one or more processes at later time.·

 Data store shown between the lines and data.

 Data store name is plural and consist noun and adjectives.ex Students, products.

 Data store connected to a process with a data flow.

*Entity Symbol:·    

  It is representing by rectangle symbol with 3D dimensional shaded shape.

  It is source/sink or external to represent source of data input and output.

  Here source means supplies data to system and sink means an entity receives data from system.

  External Entity symbol represents something connected to the information system.

*DFD Main Tasks:-

Step 1: Draw a context diagram

Step 2: Draw a diagram 0 DFD

Step 3: Draw the lower-level diagram. *Context Diagram:

• This is the first level view of information system that generates information system.
• It include only one process identify by o and like a black box that heading of whole information system.
• Around single central process we placed the external entities and use data flows to connect the entities to central process.
• In context diagram we could not show internal data store.
• We use unique names and reference number within each set of symbols and process.

*ZERO level DFD:- 

• If we want show the detail of the context black box than we need to create ZERO level DFD.
• Here we can show externally processes, data flows, data store.
• Zero Level DFD need to split down further low level DFD.

*Lower-level Diagram:- 

·    These techniques require to levelling and balancing techniques.

   Getting more and more detailed of diagram for show the process is called levelling·

    For ensuring properly input and output of data flows require Balancing.   

ANS2:The Data and Process modelling concepts are important:

• It is logical model so it will co-operate in business firm and user need.
• This modelling is divided more and more externally design of information system in graphical view. So it is very easy for developer to develop the system more comfortably.
• If it is created then it is time consuming and compress task for developer to develop system. 
• It is good when we good mapped to implement new system into old system as per user requirement.
• Modelling is very useful for all characteristics of data element to examine, easier recording, implementing data flow, processes and verifying the data at the developing time.
• Thus the modelling is important objective, responsive, and successive to implement system.

 Ans 3:  The greatest problem of data and process modelling concepts:(1)   It will take more time monthly, yearly to develop model in simpler manner.(2)   Developer can not develop system before modelling.(3)   The responsive part of creating data and process modelling concepts. Only expert technical persons can develop this model.(4)   It is cause of huge mistake when implementing the model. So it needs very responsive tasks. 

 Ans 4:(1)   Firstly we review the system and make start and simple path to make information system.(2)   We must be aware about Spontaneous genration, balck holes and Gray holes for developing the model.(3)   We must use leveling and balancing techniques for ensuring data flow input and output.(4)   We have to create input and output table for finding incoming data flow as input and outgoing data flow as output.(5)   We mention of all data flow diagram and data stores that use a particular data element. 

WEEK2-ASSIGENMENT

Question1: What are the skills and knowledge that a good systems analyst requires? 

Ans1: The skills and knowledge about system analyst is shown below: 

          >Generally A person who can provide bridge between information systems user and developers is called system analyst.

         >System Analyst should have well understands about system’ technical aspects and can assess their knowledge and skills for implementing user     requirement.

          >System Analyst should have very good interpersonal skills like, they should listen well and ask inquiring questions in an simplest manner.          

         >System Analyst Should have interpersonal skills and knowledge: That means he should relate with client idea for attracting them and solving their problem.

          > System Analyst Should have Political skills and knowledge: That means he should issues of power, organizational culture, change and conflict

.          > System Analyst Should have Systems development task skills: In this tasks he follow the Systems development life cycle process for acquire knowledge and skills like  analyze planned, Alternative analysis, design, development like acquire needed thing for creation of system, implement new system from the old system and maintenance of system like fixing errors .

           >System Analyst should have Technology skills: That means he should good knowledge and skills about identify and implement system solutions, regrading their document and review processes and procedures, ability to report on strategic direction of organization, knowledge of relation database , data warehousing, operating system. In shortly System Analyst have good knowledge and skills about the hardware, software of information systems.

          > System Analyst should have Business task knowledge: That means he should well knowledge about project management and broad project practices in different functional areas in the organization. 

Question2: How do you plan to develop those skills?

 Ans:    (a) Firstly, awarding various techniques and data sources as per requirement. Like we obtain information about exiting system and getting interview, observation, questioners to the user.

          (b) We can watch users works and get interview hourly, weekly as per needed. 

         (c)We may also create congenital questionnaires for getting hidden information.

         (d) We can planned and tracked the develop skills for process of system like,

          > committing to perform

         > planning performance 

        >Disciplined performance 

        > Tracking performance  

       > Verifying performance  

  (e) After well planned and tracked the skills of system, we may defining a standard process then   try to control the quantitatively for establishing quality of goals, achieving goals, managing performance.

[* This whole answer I referred from Information System A Management     Approach 3rd Edition by Steven R. Gordon and Judith R. Gordon           From page no314-323, And         *EXPLORING THE SYSTEMS ANALYST SKILL SET: Cynthia Lerouge,  Sandra Newton,J Ellis Blanton. The   Journal of Computer Information Systems. 
Stillwater: Spring 2005 Vol.45, Iss. 3; pg. 12, 12 pgs]

Ans 3:  I had developed a dummy system about ON LINE RAILWAY  RESERVATION SYSTEM during my last semester of my under graduation.      Before developing system I visited railway station and get day to day information about the Reservation design, Cancellation design, Security design and Train-Routing design as Railway staff requirements. After analysis information about their system, then I planning to make creation of detailed specifications for the proposed system to developed.   But I had some problem to propos system that I could not find and fixing problem like it totally time consuming. If I had planned before developing system I could have simplified the possibility of error occurrences or I could have fixed those bugs in a shortly time period. So this type of problem can be avoided if you give me theoretical and practical exposure of how to develop better system and clear understanding of current market and strategies.