السبت، 6 أكتوبر 2012

Roles of JAD Group Members


The roles of JAD group members as a project sponsor, project leader, timekeeper and clients are described below.

Project Sponsor - remember, this is the person who owns the business process. Their support and participation is crucial to the success of the JAD. In addition to the project responsibilities listed below, the project sponsor and the lead analyst can share the role of Project Leader, being equally responsible for the successful completion of the JAD. 

Project Sponsor Responsibilities 

● ensure the right clients are part of the group 

● ensure there is enough technical staff support for the project 

● ensure that software/hardware is purchased as needed for the project 

● ensure that the clients are given time off from their regular work to attend the JAD meetings and to perform the tasks they are assigned by the JAD (policy research, gathering information / opinions from other client groups, documentation, testing) 

● assign and work on policy research 

● delegate tasks to clients who are in the group 

● ensure that the client tasks are done 

● assist in the selection of test cases 

● assist in the definition of the scope and functionality 

● assist in benchmarking against current systems and external systems 

● help set up quality measures 

● evaluate whether the system is effective and efficient 

Project Leader - the project leader can make or break the project. They need to be committed wholeheartedly to the project, and to have a background knowledge of the business area and current or related information systems. They also need to be committed to The University, and to understand the implications of the project within the context of University goals. They need to be enthusiastic and objective. They need to be sensitive to political issues and able to draw out the opinions of the quiet members of the group, and to not allow any single individual to dominate the group. 

Project Leader Responsibilities 

● work with project sponsor to ensure the right people are in the group 

● ensure all roles for the group are filled 

● ensure that meetings are scheduled and publicized with agendas 

● ensure that agendas are planned and followed 

● ensure that meeting notes are taken, and published by the record keeper 

● edit the notes and make sure they are not a transcript but a concise accurate summary of decisions made (both pro and con) and issues discussed and actions to do (make sure they are available historically if a new member has to join in the middle of a project) 

● ensure that tasks are assigned and done, and that a task list is planned and executed in the sequence that it needs to be, with appropriate timelines 

● coordinate the technical efforts of the analysts on the team 

● do research prior to the meetings to make sure background information is gathered on the appropriate agenda topics 

● facilitate the meetings effectively 

Record Keeper - The record keeper takes comprehensive notes during a session, and then edits them into a concise summary of discussions and decisions. It is important that the resulting notes NOT be transcription of who said what. The role can be shared by various members of the team as needed. Often a well-facilitated meeting will have a note taking record keeper, and also someone who records points on an easel pad. The easel pad serves as a ready reference to the group when summarizing discussions, and for return reference on complex points. And it also is a means for the record keeper to evaluate the accuracy and thoroughness of their notes. 

Record Keeper Responsibilities 

● take accurate and thorough notes during the meeting 

● ask for clarification on points if anything is not clear 

● summarize and condense the notes after the session 

● ensure that the JAD leader and project sponsor or other relevant people proof and edit the notes prior to publishing 

● publish the notes for all current members of the team and for any other interested parties 

● keep a history of the notes for the benefit of any members who join the team in mid-project 

● remind the group if they contradict earlier decisions and make sure they know they are in contradiction. 

Timekeeper - The Timekeeper is responsible for keeping the meeting running on time and helping the group use time wisely. 

Timekeeper Responsibilities 

● makes sure the meeting begins and ends on time 

● help the meeting stay on time for each topic on the agenda 

● reminds the group that they need to end a discussion in order to have time to summarize and create an action plan in the final minutes of the meeting 

Clients - Clients are here because this is a system they use. They understand how this system is used in the real world. They will help the group understand all the tasks handled by the system, correct any misperceptions, search for oversights and supply details. Remember, no detail is too small to mention. Sometimes minor details make a major difference in the way the system should work. 

Typical Client Responsibilities 

● describe the sequence of events in a business process as it affects their office 

● describe the decisions that have to be made in a business process 

● define the information that the process has to deal with 

● define what is critical vs. what would be nice for the first version of the system 

● bring up any problems that exist in the current process or any opportunities for making it more efficient 

● research policy questions when a new business procedure is being proposed 

● analyze if there are any obstacles to success in the current environment of their office for implementing the new system 

● create test cases for testing 

● run test scripts on the cases 

● give the developers feedback on the usability and accuracy and effectiveness of the system in an organized, documented way 

● help prepare documentation on how the system works from a client's point of view 

● help prepare and implement training for other clients 

All Team Members - have the following responsibilities: 

● Commitment to the team 

● Regular attendance 

● Actively listen 

● Actively participate 

● Identify concerns 

● Brainstorm ideas 

● Recommend solutions 

● Agree upon a design by consensus 

● Assist with project duties 


Who is involved in a JAD?


The persons who are involved in JAD are sponsor, business users, real end users, system analysts and are described below.


Sponsor - this is the executive who charters the project, the system owner. They must be high enough in the organization to be able to make decisions and provide the necessary resources and support for the project. 


Business Users - the intended users of the system being designed. They are here because of their business expertise. There are two kinds of Business Users; Real End Users and Big Picture Users.


Real End Users will have to use the new system to do their jobs. Big Picture Users understand the standards and methodologies of the business functions. It is important to have both types of users, if you only have Big Picture Users you will end up with a great theoretical model of how things should work, but it may not work in practice, if you just have Real End Users, you will get a good system for today, but it may not work a year or two down the road. 


Systems Analysts - Provide non-technical explanations that help other JAD members understand and fully utilize the technology available. Monitor design for ease of use/maintenance and adherence to standards. Provide Hardware/software development.



What is a JAD?



JAD Definition: Joint Application Development (JAD) is a management process which helps Information System work effectively with users to develop information technology solutions that really work.


JAD Purpose: to define the project, design a solution, and monitor the project until it reaches completion.


JAD Philosophy: The JAD process is based on four simple ideas: 
  • People who actually do a job have the best understanding of that job. 
  • People who are trained in information technology have the best understanding of the possibilities of that technology. 
  • Information systems and business processes rarely exist in isolation. They transcend the confines of any single system or office and effect work in related departments. People working in these related areas have valuable insight on the role of a system within a larger community. 
  • The best information systems are designed when all of these groups work together on a project as equal partners. 

JAD Scope - The JAD should cover the complete development life cycle of a system. The JAD is usually a 3 to 6 month well-defined project. For large-scale projects, it is recommended that the project be approached incrementally, and that separate JAD's be used for each increment.


الخميس، 4 أكتوبر 2012

What is a Systems Analyst? & What Does A System Analyst Do?

  • Systems analysts are people who understand both business and computing.
  • Systems analysts study business problems and opportunities and then transform business and information requirements of the business into the computer-based information systems and computer applications that are implemented by various technical specialists including computer programmers.
A formal definition:
  • A systems analyst facilitates the study of the problems and needs of a business to determine how the business system and information technology can best solve the problem and accomplish improvements for the business. The product of this activity may be improved business processes, improved information systems, or new or improved computer applications frequently all three
  • When information technology is used, the systems analyst is responsible for:
    • the efficient capture of data from its business source
    • the flow of that data to the computer
    • the processing and storage of that data by the computer
    • the flow of useful and timely information back to the business and its people
  • Information technology is a contemporary term that describes the combination of computer technology (hardware and software) with telecommunications technology (data, image, and voice networks).
What Does A System Analyst Do?
  • A system analyst is a system-oriented problem solver.
    • System problem solving is the act of studying a problem environment in order to implement corrective solutions that take the form of new or improved systems.
  • Most systems analysts use some variation of a system problem solving approach called a system development life cycle.
    • A systems development life cycle (SDLC) is a systematic and orderly approach to solving system problems.

The SDLC usually incorporates the following general-purpose problem solving steps:
  • Planning - identify the scope and boundary of the problem, and plan the development strategy and goals.
  • Analysis - study and analyze the problems, causes, and effects. Then, identify and analyze the requirements that must be fulfilled by any successful solution.
  • Design - if necessary, design the solution not all solutions require design.
  • Implementation - implement the solution.
  • Support - analyze the implemented solution, refine the design, and implement improvements to the solution. Different support situations can thread back into the previous steps.
What is a user?
  • A user is a person, or group of persons, for whom the systems analyst builds and maintains business information systems and computer applications. A common system is client.
  • There are at least two specific user/customer groups: system users and system owners.
    • System users are those individuals who either have direct contact with an information system or application or they use information generated by a system.
    • System owners provide sponsorship of information systems and computer applications. In other words, they pay to have the systems and applications developed and maintained. 

الثلاثاء، 2 أكتوبر 2012

Implementation of Data structure


There are three levels of implementation of data structures which are:



  1. The Abstract Level:– The abstract(or logical) level is the specification of the data structure-the "what" but not "how". At this level, the user or data structure designer is free to think outside the bounds of anyone programming language.
  2.  Application Level:– At the application of user level, the user is modeling real-life data in a specific context.
  3.  Implementation Level:– The implementation level is where the model becomes compatible, executable code.

You Might also view the following Related Posts

    For more other Posts: Click Here



    الاثنين، 1 أكتوبر 2012

    What is data structure?


    A data structure is the organization of data in computers memory or in a file.

    Some examples of data structures are: array, stack, queue, link list, binary tree, hash table, heap and graph. Data structures are often used to build databases. Typically, data structures are manipulated using various algorithms.

    Based on the concept of Abstract Data Types (ADT), we define data structure by the following three components

    1. Operations: Specifications of external appearance of data structure
    2. Storage structures: Organizations of data implemented in lower-level data structures.
    3. Algorithms: Description on how to manipulate information in the storage structures to obtain the  results defined for operations.

    You Might also view the following Related Posts

    For more other Posts: Click Here

    Basic Components of operating Systems.

    The basic components of operating systems are.
    a) Process Management:  
    The operating System is responsible for the following activities in connection with process management.
    · Process creation and deletion 
    · Process suspension and resumption 
    · Provision mechanisms for process synchronization and process communication

    b) Main-Memory management  
    The operating system is responsible for the following activities in connection with memory management. 
    · Keep track of which parts of memory and currently being used by whom 
    · Decide which process to load when memory space becomes available. 
    · Allocate and De-allocate memory space as needed.

    c) Secondary-Storage management  
    The operating system is responsible for the following activities in connection with disk management. 
    · Free space management 
    · Storage allocation 
    · Disk scheduling

    d) I/O system Management 
    The I/O system management consists of 
    · A buffer-caching system 
    · A general device-driver interface 
    · Drivers for specific hardware devices

    e) File Management 
    The operating system is responsible for the following activities in connection with file management. 
    · File creation and deletion 
    · Directory creation & deletion 
    · Support of primitives for manipulating files and directories 
    · Mapping files onto secondary storage 
    · File backup on stable (non volatile) storage media.

    f) Protection system 
    Protection refers to a mechanism for controlling access by programs, processes or users to both system and user resources. 
    The protection mechanism must. 
    · Distinguish between authorized and unauthorized usage. 
    · Specify the controls to be imposed. 
    · Provide a means of enforcement

    g) Networking (Distributed System)

    A distributed system is collection of processors that do not share memory or a clock. Each processor has its own local memory. The processors in the system are connected through a communication network. A distributed system provides user access to various system resources. Access to a shared resource allows. 
    · Computation speed-up 
    · Increased data availability 
    · Enhanced reliability

    h) Command-Interpreter system 
    Many commands are given to the operating system by control statements which deal with. 
    · Process creation and management 
    · I/O handling 
    · Secondary-storage management 
    · Main-memory management 
    · File system access 
    · Protection 
    · Networking 
    The program that reads and interprets control statements called variously 
    · Control-card interpreter 
    · Command-line interpreter 
    · Shell(in UNIX)

    You Might also view the following Related Posts

    For more other Posts: Click Here