I have some questions in systemm analysis and design class i need answers for it
ID: 3677201 • Letter: I
Question
I have some questions in systemm analysis and design class i need answers for it as soon as posible please.
1- what is JAD & RAD? list an advantage & disadvantage of each.
2- what is included in a System requirement checklist? give an example of each.
3- what is the relationnship between a context diagram and diagram 0? what symbol is not used in a context diagram?
4- describe a data dictionary and give examples of what is included.
5- what decisions might management reach at the end of the systems analysis phase, and what would be the next step in each case?
Explanation / Answer
1)
1. Joint Application Design (JAD) (developed by IBM in late 1970's) is a technique ensuring that information is gathered from all affected parties, and that requirements that are received in outcome are approved by all participants, and not only by decision of system analysts collecting the requirements.
2. JAD brings team approach into play gathering users from various departments and IT specialists together in 3-to-1 ratio for a structured work session. It allows users to share their opinions on the current system, and gives a chance through shared purpose to come to a consensus on what needs to be changed
3. In addition, JAD systematizes the systems requirement process, solving project managers dilemma of uniting disciplined approach to systems analysis with flexible user coordination.
4. JAD decreases time and costs associated with requirements elicitation process. During 2-4 weeks information not only is collected, but requirements, agreed upon by various system users, are identified.
5. Experience with JAD allows companies to customize their systems analysis process into even more dynamic one like Helix, a methodology for mission-critical work.
6. Systems analysts always have to keep in mind that none of techniques they use are a full-proof way to acquire the information, neither is JAD. Many proponents of modern systems analysis feel that JAD can be ineffective if not used correctly.
7. RAD model is Rapid Application Development model.It is a type of incremental model. In RAD model the components or functions are developed in parallel as if they were mini projects. The developments are time boxed, delivered and then assembled into a working prototype.
8. This can quickly give the customer something to see and use and to provide feedback regarding the delivery and their requirements.
9.Advantages of the RAD model:
10. Disadvantages of RAD model:
2)
1. When developing systems requirements, a good rule of thumb is to provide designers and test engineers with what they must know, but leave as much "white space" as possible for clever designers to explore design options (many times through prototypes of different forms or experiments).
2. An obvious place to start developing system requirements is with the user requirements—high-level expressions of user needs that the system is expected to satisfy.
3. Examples of Department of Defense (DoD) user requirement sources include the initial capabilities document (ICD), the capability development document (CDD), and the capability production document (CPD).
4. There are two cautions when working with user requirement documents. First, the needs are frequently expressed in user operational lingo that may not be meaningful to engineers. An even more insidious problem is that while the language may be meaningful to both operators and engineers, it may also convey different interpretations, resulting in a lack of clarity about intent by the operators and the engineers.
5. Systems engineers need to explicitly account for and resolve this language divide and may have to translate operational terminology into engineering requirements. Second, user requirements often are not expressed in ways that unambiguously cover acceptance or test criteria.
6. What appears to be a clear user requirement (e.g., "detect airborne objects out to a range of 100 miles") often requires the systems engineer to do substantial work to achieve a set of requirements that are testable and can be built with reasonable technological risk.
3) A context diagram provides the most general view of an information system and contains a single process symbol, which is like a black box. A diagram 0 shows the details inside the black box. A diagram 0 zooms in on the context diagram and shows the major processes, data flows, and data stores. It also repeats the external entities and data flows that appear in the context diagram. Data store symbols are not used in context diagrams because data stores are internal to the system.
4) A data dictionary, or Metadata Repository, as defined in the IBM Dictionary of Computing, is a "centralized repository of information about data such as meaning, relationships to other data, origin, usage, and format."[1] The term can have one of several closely related meanings pertaining to databases anddatabase management systems (DBMS):
5) To complete the system analysis phases, you must prepare the system requirements document and then make your presentation to management. (System requirements document and Presentation to management) Management probably will choose one of five alternatives: develop an in-house system, modify a current system, purchase or customize a software package, perform additional systems analysis work, or stop all further work. Depending on their decision, your next task as system analysts will be one of the following: Management will choose one of the following;
1. Implement…an outsourcing alternative. If outsourcing is selected, you will work with representatives of the services provider to achieve a smooth transition to the new environment.
2. Develop…an in-house system. Begin systems design tasks.
3. Purchase…or customize a software package. Negotiate the purchase terms with the software vendor for management approval. Then, if the package will be used without modification, you can begin planning the systems implementation phase. If you make modifications to the package, your next step is to start the system design phase. If the vendor will make the modifications, then your next step is to start planning the testing and documentation of the modifications as part of the systems implementation phase
4. Perform…additional system analysis work. Management might want you to investigate certain alternative further explore alternatives not examined develop a prototype, reduce the project scope because of cost constraints, or expand the project scope based on new development. If necessary, you will perform the additional work and schedule a follow-up presentation.
5. Stop ….all further work. The decision might be based on your recommendation, a shift in priorities or costs, or for other reasons. Whatever the reason, if that is management’s decision, then you have no additional tasks for the project other than to file all your research in a location so it can be retrieved if the project is reopened in the future.