week2ans

week12

s0103357 — Fri, 06 Oct 2006 01:51:29 +0000

answer1: The system analyst should have the following skills:

have an extensive knowledge of hardware, software and programming
be able to gather and interpret data
have excellent communication skills, for discussing ideas with colleagues from technical and non-technical roles, and clients
have excellent analytical skills and creative approach to problem solving
have good negotiating skills
be able to plan and manage a project
have an appreciation of wider business demands
be able to work within a budget
be willing to update skills in line with developments within the sector
be able to work as part of a team.

answer 2: the answer in week 2 provide the broad knowledge of skills of system analyst but now it provides comprehensive details of skills of analyst.

answer3: i did not strictly followed the gnatt chart because of lots of assignments.

answer4:i think there should be more focus on concepts like ERD and DFD because there was less time for them and they are a bit difficult.

week 11

s0103357 — Mon, 02 Oct 2006 12:12:42 +0000

answer 1:

Throughout the whole course we have studied how to develop information system using System Development Life Cycle (SDLC) and other analytical and graphical tools like DFD(Data Flow Diagrams),ERD(Entity Realationship Diagram) that assist the anlyst in developing a new system. We have learnt about the various IT developments and trends,different phases of SDLC i.e system planning, system analysis, system design, system implementation, system operation and support.

answer 2:These concepts are important because a system cannot be developed without using these concepts.these concepts assist the analyst in developing new systems,help the analyst to evaluate the system being developed.

answer3:The difficult topic that creates some problem to me is data flow diagrams, normalization and cardinality in entity relationship diagrams. That seems difficult to me little bit in whole course.

answer4: But by practicing them I think they didn’t remain that much hard for me now.

week10

s0103357 — Sat, 23 Sep 2006 03:42:49 +0000

Comparision and contrast of traditional and agile methods

Agile methods are adaptive rather than predictive. Traditional methods tend to plan out a large part of the software process in great detail for a long span of time. So these systems resist changes. whereas the agile method welcomes change because processes in agile methods adapt and thrive on change.
Agile methods are people-oriented rather than process-oriented. The goal of traditional methods is to define a process that will work well irrespective of who is using it.on the other hand,in agile methods the role of a process is to support the development team in their work.
In Agile methods completion of next release is predictable whereas in traditional methodology duration of whole project is prdictable.
Activities in agile methods are often context dependent on the other hand in trdaitional methodolgy activities are repetitive.
In both agile and traditional methodology process performance is reliable.
In both the methodologies processes have specificable interactions.

week 8

s0103357 — Sat, 09 Sep 2006 14:36:05 +0000

http://en.wikipedia.org/wiki/Agile_Software_DevelopmentI

In this link it is written under topic, agile software development uses number of software development methods as it didn’t depend on one particular method. It uses a approach in which software is made in short iterations so that it can be released as early as possible like in few weeks not in months like in traditional software development systems. There emphasis is on fast delivery of software to customers, measuring performance on the based of working of software, adaptability to frequent changes in requirements and interaction between business people and developers. And lastly agile software development is based on adaptive methods as when project changes are occurred then it will easily be done in this system

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

Authors written in IEEE computer society under agile software development that this approach is better suited in changing environments in organizations and it reduces cost of changes throughout the project and will produce better design quality of software. Testing is conducted regularly so that it results less expensive to the organization if it will be done later and have to face lots of problems that will be tuff to handle then.

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

Authors written in Growing Systems in emergent organizations that how the organizations changing from there state of stability to emergent as they are never become stable as they are continuously in process of changing conditions. The organizations are in regular changing conditions and if they didn’t adapt to these changes then it will prove bad results. And Information technology plays vital role in this.

week6 answers

s0103357 — Sun, 03 Sep 2006 12:25:18 +0000

A good user interface design is based on a combination of ergonomics, aesthetics and interface technology.(Shelly G, Cashmen T & Rosenbolt h,2006). CQU’s information system covers these three things very perfectly. The interface of CQU information system is very easy to learn and use. It contains features that make it effective, efficient, error tolerant. The outlook of e.rolment, MyCQU is very clear as all controls, buttons and icons are labeled clearly. It is easy to navigate or return to any level in the menu structure.Various control features like command buttons, dialog boxes, list boxes, calendar controls make it easy for students to use the system. It also provides feedback to students wherever required For e.g while submitting online assignment students can see the progress of their file uploading and after submitting the assignment they can also check their submission. Similarly in MyCQU students can verify their personal information and timetable whenever they need. The interface of system is focused on basic objective i.e to provide information to students. Students can access all the information of the university easily at any time and they can also communicate with the staff and faculty easily using information system only. The output provided by the CQU system is also very specific,adequate,correct and complete. To conclude, CQU information system is providing all the information to the user very effectively and efficiently

week7

s0103357 — Sun, 03 Sep 2006 12:24:09 +0000

Answer1:The most important concept we learned this week is ERD(Entity Relationship Diagram).An ERD is a data modelling technique that shows entities and realtionships between them in graphical form. So an ERD consist of entiriy and realtionship.

An entity is a erson,object,place or event for which data is collected.It is represented by a single rectangle.Entities are of two types Strong and weak.A strong entity is one whose existance do not depend on any other entity.A weak Entity on other hand is dependent on some other entity.It cannot exist independently.Entities have properties that are known as attributes.for eg customer is an entity whose attributes can be customer_no,customer_id,customer_address etc.

An attribute that uniquely identify an entity is called the key attribute.eg customer_id.Attributes can be multivalued also.

An relationship illustrates how entities share information.It can be unary,binary,ternary,N-ary.

The other most important component of ERD is CARDINALITY.Cardinality specifies how many instances of an entity relate to one instance of another entity.In other words it represents realtionships between the entities in terms of numbers.Mainly there are three kind of cardinal relationships.these are one to one (1:1),one to many(1:M) and many to many(M:M).

Answer2:ERD is important because it provide overview of the system showing logical relationships between the system entities and moreover it is graphical represntation that makes the system easy to understand and supports business operations.

Answer3:The main problem i am facing in ERD’s is while deciding what are entities to take and in defining the realtionships between them i.e cardinality.I always define the cardinality in reverse order.

Answer4:These problems i think can be solved by trying making ERD’s because in this weeks tutorial we made ERD’s and by practising the examples given in tutorial lots of my doubts got cleared.

s0103357 — Mon, 21 Aug 2006 05:07:30 +0000

week6

s0103357 — Mon, 21 Aug 2006 05:06:19 +0000

week 4 answers

s0103357 — Tue, 08 Aug 2006 01:23:10 +0000

Answer 1:The most important concepts that we learnt about data and process modeling is DFD(Data Flow diagram) and DD(Data dictionary). DFD is most common tool used for process modeling. DFD is a graphic that illustrates the movement of data between external entities and the processes and data stores within. It uses only 4 symbols to represent both physical and logical Information Systems. These symbols represent Data Flows, Data Stores, Processes and Source/Sinks. A DATA FLOW is data that are in motion and moving from one place in a system to another.A DATA STORE is a data at rest. It may represent one of many different physical locations for data.A PROCESS is the work or action performed on data so that they are transformed, stored A SOURCE/SINK is the origin and/or destination of the data. There are certain rules governing DFD’s. These are as follows:1) No process can have only outputs.2) No process can have only inputs.3) A process must have a verb phrase label.4) Processes must be numbered.5) Data cannot directly move from one data source to another.6) Data store must have a noun phrase label.7) Data cannot move directly from source to a sink. They must be moved by a process. A Source/Sink has a noun phrase label9) A data flow has only one direction of flow between symbols. 10)A data flow has a noun phrase label.We can also decompose a DFD to primitive level. The boundary or scope of system, the system’s relationship to its environment is represented by DFD called CONTEXT DIAGRAM. Context diagram contains only 1 process and no data stores. And the process must be labeled “0” in context diagram. A DFD produces the logical model of the system but details within those DFD’S are documented separately in a data dictionary. Data dictionary is a DATA REPOSITORY. It is central storehouse of information about system data.

ANSWER 2: These concepts are important because · There must be some meaningful representation of the information system of the system that exists and requirements desired in the new system that is easy to understand.· These tools are important to establish specifications of the Information System· They accurately reflect the information system being modeled.· They help in better understanding of the system.· These are very useful in documentation ANSWER 3:The only problem am facing is in breaking down the DFD’s into primitive levels. ANSWER 4: I think this problem can be solved by practicing and asking the tutor wherever necessary or by taking help of friends.

gnatt view 2

s0103357 — Tue, 08 Aug 2006 01:19:48 +0000