A feasibility study is carried out
1.after final requirements specifications are drawn up
2.during the period when requirements specifications are drawn up
3.before the final requirements specifications are drawn up
4.at any time
All information required can be gathered in
1.one interview
2.two interviews
3.several interviews
4.several interviews and group discussions
Among information gathering methods, interviewing is essential as
1.it gives an opportunity to question the interviewees and clarify details and doubts the analyst may have
2.it can be easily arranged
3.it is recommended by senior analysts
4.it is necessary to meet everyone in the organization
An organization requests an information system to be designed when
1.there is a change in management
2.it is dissatisfied with the current system as it does not meet their information requirement
3.the current system has been working for 2 years
4.new software tools are introduced in the market
Changing an operational information system is
1.impossible
2.expensive and done selectively
3.never required
4.usually done
Data flow diagrams are developed by
1.systems analyst
2.programmers
3.system designers
4.users and managers of an organization
Data flow diagrams are usually developed during
1.system design phase
2.feasibility study
3.implementation phase
4.systems analysis phase
Document flow diagrams are developed by
1.systems analyst
2.programmers
3.system designers
4.users and managers of an organization
Document Flow Diagrams are used to depict
1.how and when documents flow in the organization
2.various offices/entities of an organization and the documents as well as physical items which flow between these entities
3.what documents flow in an organization
4.how documents are generated and flow in an organization
Document flow diagrams are usually developed during
1.System design phase
2.Feasibility study
3.Implementation phase
4.Fact gathering phase
During interviews an analyst must
1.gather information on user requirements, procedures and practices
2.tell the user what is good for organization
3.tell the user how to run the organization
4.tell the user what is wrong with the organization
Final specifications are drawn up by
1.system analyst in consultation with the management of the organization
2.the managers of user organization
3.system analyst in consultation with programmers
4.system designers along with users
Hardware study is carried out
1.after the final system is specified
2.at the requirements specification stage
3.before the requirements are specified
4.whenever management decides it is necessary
In a document flow diagram a dashed line with an arrow depict
1.flow of documents
2.control flow
3.flow of materials
4.data flow.
In a document flow diagram a solid line with an arrow depicts
1.flow of documents
2.control flow
3.flow of materials
4.data flow.
In a document flow diagram arrows are necessary to depict
1.how documents flow
2.direction of flow of documents
3.when documents flow
4.whether documents flow or not
In a document flow diagram entities are represented by
1.circles
2.rectangles with rounded edges
3.diamond shaped boxes
4.rectangles
In order to understand the working of an organization for which a computer based system is being designed, an analyst must
1.look at only current work and document flow in the organization
2.discuss with top level and middle level management only
3.interview top, middle, line managers and also clerks who will enter data and use the system
4.only clerical and middle level staff who have long experience in the organization and will be users of the system
Information is gathered by a system analyst in order to
1.find out whether a computer based system is required
2.find out how the organization works
3.find out how the current system works and what is expected from a new computer based system
4.find out who will use the system
Information is gathered for computerization during
1.requirements determination phase
2.systems design phase
3.implementation phase
4.feasibility phase
Initial requirements specification is
1.not changed till the end of the project
2.continuously changed during project implementation
3.only a rough indication of the requirement
4.changed and finalized after feasibility study
Interviews are essential to gather
1.quantitative information
2.qualitative information
3.facts and figures
4.statistical information
It is good idea for a system analyst
1.to define the objectives of the information system
2.to tell the users what the objectives should be
3.to let the user formulate the objectives of the information system being designed
4.not to worry about the objective during the interviews
It is necessary to carry out a feasibility study as
1.top management can not ensure that a project is feasible before calling a system analyst
2.top management is not sure what they want from the system
3.even though top management is in favor of the system, technology may not be mature for implementation
4.all organizations do it
It is necessary to consult the following while drawing up requirement specification
1.only top managers
2.only top and middle management
3.only top, middle and operational managers
4.top, middle and operational managers and also all who will use the system
It is necessary to design an information system to easily accommodate change, because
1.new computers are introduced every year
2.new computer languages become popular every year
3.organizations' requirements change over a period of time
4.systems need continuous debugging
It is necessary to gather
1.quantitative information only as qualitative information is usually biased
2.both qualitative and quantitative information
3.qualitative information only as it is easily available
4.qualitative information only as quantitative information is usually not correct
It is necessary to interview top level managers as the first step in information gathering
1.otherwise you will not get cooperation
2.they can give you an overview of the organization and specify objectives of the system
3.they are usually not available
4.the number of persons to be interviewed at top level is small
It is necessary to prioritize information requirements of an organization at the requirements determination phase as
1.it is always good to prioritize
2.there are conflicting demands from users
3.there are constraints on budgets, available time, human resource and requirement
4.all good organization do it
Managers in organizations should not design their own systems as
1.systems have to interact with other systems
2.they do not have the special skills necessary to design systems
3.it is not their job
4.they are always very busy
Sending questionnaires are the good means of gathering
1.quantitative data
2.qualitative data
3.both quantitative and qualitative data
4.data from top management
System approval criteria are specified
1.when the final specifications are drawn up
2.during feasibility study
3.during the requirements specifications stage
4.during system study stage
System design is carried out
1.as soon as system requirements are determined
2.whenever a system analyst feels it is urgent
3.after final system specifications are approved by the organization
4.whenever the user management feels it should be done
System evaluation is carried out
1.after the system has been operational for a reasonable time
2.during system implementation
3.whenever managers of user organization want it
4.whenever operational staff want it
System Requirements Specification is developed by
1.users of the proposed system
2.top level managers of an organization
3.examining the functioning of similar organizations
4.systems analyst after information gathering phase in consultation with users
System test plan is specified
1.when the final specifications are drawn up
2.during feasibility study
3.during the requirements specifications stage
4.during system study stage
The expansion of SRS is
1.System Requirements Specification
2.System Resources Statement
3.Statement of Reliability of System
4.Standard Requirements Statement
The final specifications are arrived at
1.after feasibility study
2.during feasibility study
3.just before implementation phase
4.when the system is being designed
The main goal of arriving at a final specification is
1.to tell the organization's managers how the system will function
2.to tell the organization's managers what the proposed system will achieve in a language understood by them
3.to compute the cost of implementing the system
4.to assist in designing the system
The main objective of feasibility study is
1.to assess whether it is possible to meet the requirements specifications
2.to assess if it is possible to meet the requirements specified subject to constraints of budget, human resource and hardware
3.to assist the management in implementing the desired system
4.to remove bottlenecks in implementing the desired system
The main objective of system evaluation is
1.to see whether the system met specification
2.to improve the system based on operational experience for a period
3.to remove bugs in the programs
4.to asses the efficiency of the system
The main objective of system modification is
1.to use the latest software tools
2.to meet the user's new/changed needs
3.to use the latest hardware
4.to have the most modern system
The main objective of System Requirements Specification is to
1.enable a systems analyst to satisfy himself and the user that they have mutually understand the user's information requirements
2.write down the requirements clearly
3.estimate the cost of developing the system
4.to make sure that it is possible to develop the system
The most difficult information to gather in an organization is
1.that which is known to only few persons in an organization
2.that which is not written down in an organizational manuals
3.company confidential information
4.what is consumed as obvious by the managers in an organization
The most important attribute of a systems analyst is
1.excellent programming skills
2.very good hardware designing skills
3.very good technical management skills
4.very good writing skills
The primary objective of system design is to
1.design the programs, databases and test plan
2.design only user interfaces
3.implement the system
4.find out how the system will perform
The primary responsibility of a systems analyst is to
1.specify an information system which meets the requirements of an organization
2.write programs to meet specifications
3.maintain the system
4.meet managers of the organization regularly
The purpose of designing an information system is to
1.modernize the functioning of an organization
2.reduce the number of people employed by an organization
3.provide operational, tactical and strategic information to efficiently manage an organization
4.improve the day-to-day working of an organization
The role of a system analyst drawing up a requirements specification is similar to
1.architect designing a building
2.a structural engineer designing a building
3.a contractor constructing a building
4.the workers who construct a building
To easily modify the existing system it is necessary to
1.use good software tools
2.use the best hardware available
3.design the system which can be changed at low cost
4.keep the programming team happy