INSY Flashcards
set of detailed methods, procedures, and routines establishes or formulations to carry out a specific activity, perform a duty, or solve a problem
System
- The dissection of a system into its component pieces to study how those component pieces interact and work
- Survey and planning
- Study and analysis
- Definition
System analysis
- The process of defining architecture, components, modules, interfaces and data for a system to satisfy specified requirements.
System Design
- Installing a system without proper planning leads to great user dissatisfaction and frequently causes the system to fall into disuse
true
any person who has interests in an existing or proposed information system.
- May include both technical an non-technical workers
- May also be internal ones or may be the external one
SYSTEM STAKEHOLDERS
the individual responsible for the overall procurement, development, integration, modification, operation, maintenance, and retirement of an information system
System owner
person who interacts with a system, typically through and interface, to extract some functional benefit.
- System users
Clerical and service workers
Technical and professional staffs
Supervisors, middle managers and executive managers
a. Internal system users
Customer
Suppliers
Partners
Employees
b. External system user
person in charge of the system’s architectural, logical, and physical design to satisfy specified requirements.
- System designers
persons involved in designing and writing computer programs that allow the computer hardware to interface with the programmer and the user, leading to the effective execution of application software on the computer system.
- System builders
professional who specializes in analyzing, designing and implementing information systems
* A person who uses analysis and design techniques to solve business problems using information technology.
- System analysts
managers, external companies, system stakeholders, users, vendors and suppliers, software programmers, and technical specialists.
SYSTEM ANALYST ROLES & QUALITIES
- The analyst plays a key role in information system development projects
- Must understand how to apply technology to solve business problems
- May serve as change agents who identify organizational improvement.
Roles of a system analyst
- Problem solver
- Communicator
- Strong personal and professional ethics
- Self-disciplined and self-motivated.
Qualities of the system analyst
support day-to-day operations of the company
Operational level
it is a large amounts of data for routine business transactions
- Transaction processing system
supports data workers who share information, but do not usually create new knowledge
- Office automation system (OAS
supports professional workers such as scientists, engineer, and doctors
- Knowledge work system (KWS)
an organized collection of people, procedures, software, database, and devices used to provide routine information to managers and decision-makers
- Management information system (MIS)
aids decision-makers in the making of decisions.
- Decision support system (DSS)
captures and uses the knowledge of an expert for solving a particular problem, which leads to a conclusion or recommendation.
Expert system
helps executive to make unstructured strategic decisions in an informed way.
- Executive support system (ESS)
permit group members to interact with electronic support
- Group decision support system (GDSS)
it may include software support called “groupware” for team collaboration via network companies.
- Computer-supported collaborative work system (CSCWS)
Is a framework that is used to structure, plan, and control the process of developing an information system.
System development methodology
- is a standard step when developing systems such as planning, analysis, design, implementation, and maintenance.
System development cycle (SLDC)
process of defining clear, discrete, activities, and the work needed to complete each activity within a single project
- Planning phase
understand and document the business needs and the processing requirements
- Analysis phase
database, system flow, core system features, user interface and usability, network and its requirements.
- Design phase
specifically targets the system creation process: the developers write code and build the app according to the finalized requirements and specification documents.
- Development phase
- Includes the front end and back end developing processes, along with core functions that software should feature, includes UI/UX design of the application, all the basic qualities the product must provide for its end-users.
- Development phase
- Though this phase my seem a little bit straightforward, it’s still possible to implement the minor changes and improvements if there are any.
- Development phase
after the software is build, it is even more important to make sure all its features work correctly and coherently, and cannot negatively affect the user experience
- Integration and testing phase
- Involves detecting the possible bugs, defects and errors, searching for the various vulnerabilities, etc. and can sometimes take up even more time compared to the app-building stage.
- Integration and testing phase
once the product is ready to go, it’s time to integrate It into the specific environment, which usually means its install. At this stage, the software completes the final testing through the training environment, after which its ready for the presentation on the market
- Implementation phase
keep the system running productively during the years following its initial installation. Upgrades or enhancements may be carried out to expand the system’s capabilities
- Maintenance phase
this structure describes a development method that is linear and sequential.
- Traditional waterfall model
- Based on the metaphor that when one phase Is finished, the development proceeds to the next phase and there is no going back
Traditional waterfall model
- Does not accept changes and revisions that become necessary with most projects
Traditional waterfall model
attempt to capture and use the dynamics of changes inherent in software development in the process itself rather than resisting the ever-present and quickly changing environment. Communication is critical.
- Agile methodology
looks at the system from the bottom-up view
- The procedure of identifying software engineer requirements and developing software specifications in terms of a software system’s object model.
- Must specify some data organization of attributes and procedural description of each operation
- Object-oriented analysis and design (OOAD)
is one of the most important and vital aspects of any research study.
– is the basic unit in statistical studies
- Data
involves observing people/conditions through rapid assessment or case studies.
- Costly because the researcher has to spend a long period of time studying the subject
A. Observation
person to person contacting asking either closed-ended or open-ended questions
- face-to-face / online interview
data is collected by the interviewer through telephone.
- Telephone interview
sending interview forms or questionnaires by mail.
- Mailed questionnaire
- Records kept by the respondents
- Records of data from experiments
- And records of agencies or institutions can be examined to gather relevant information.
C. Examining records
– targeted group of individuals
- Selected and knowledgeable persons (normally groups of men and women are interviewed as a group).
D. Focus group discussions
series of prepared written question to solicit answers to the needed information about the research problem.
- it is self-administered
- Questionnaire
– a structured set of questions which are usually asked orally and recorded by the interviewer in writing, or with the use of audio or video recorders.
- Interview schedule
contains keywords or questions that the interviewer will ask the respondents which are predominantly open-ended
- Interview guide / checklist
DATA COLLECTION INSTRUMENTS
QUESTIONNAIRE, INTERVIEW SCHEDULE, INTERVIEW / CHECKLIST
