Sub.

Code: 10162
SYSTEM ANALYSIS AND DESIGN
1. Explain the characteristics of system concepts.
ANS

​ Interrelated Components:
● Systems consist of multiple components or elements that are interrelated and
work together to achieve a specific purpose or goal. These components can
include hardware, software, people, data, and procedures.
​ Objective or Purpose:
● Every system is designed with a specific objective or purpose in mind. It exists to
fulfill certain goals or meet the needs of its users or stakeholders.
​ Boundary:
● Systems have boundaries that define what is inside and outside the system. The
boundary helps to distinguish the system from its environment, and it is crucial
for understanding system interactions.
​ Input-Process-Output:
● Systems typically have input, process, and output stages. Inputs are resources or
data that enter the system, processes are the activities that transform inputs into
outputs, and outputs are the results produced by the system.
​ Feedback:
● Systems often incorporate feedback mechanisms to monitor and regulate their
performance. Feedback helps the system adjust and adapt to changes in its
environment or correct deviations from the desired output.
​ Control:
● Systems have control mechanisms that regulate and manage the operations of
the system. This ensures that the system behaves in a predictable and desired
manner.
​ Hierarchy:
● Systems can be organized hierarchically, with subsystems or modules that
perform specific functions. The hierarchy helps in managing complexity and
breaking down the system into manageable components.
​ Environment:
● Systems operate within an environment, which includes external factors and
influences. Understanding the relationship between a system and its environment
is crucial for effective system design and management.
​ Emergent Properties:
● Systems often exhibit emergent properties, which are characteristics or
behaviors that arise from the interactions of the system's components but are not
present in the individual components themselves.
 ​ Adaptability:
● Systems need to be adaptable to changes in their environment or requirements.
This adaptability ensures that the system remains effective and relevant over
time.

Understanding and considering these characteristics is essential for designing, analyzing, and

managing systems effectively. These concepts are foundational in various fields, including

information systems, engineering, biology, and management.

2. Explain any two fact finding techniques. Give its advantages and disadvantages.
ANS

Certainly! Fact-finding techniques are methods used to gather information about a

system, process, or problem during the analysis phase of system development. Two
common fact-finding techniques are interviews and document analysis.

​ Interviews:
Advantages:
● Rich Information: Interviews allow for in-depth, qualitative information
gathering. The interviewer can ask follow-up questions and seek
clarification, leading to a more comprehensive understanding of the
subject.
● Interpersonal Interaction: Direct interaction with individuals provides an
opportunity to build rapport, trust, and a deeper understanding of the
stakeholders' perspectives and concerns.
● Flexibility: Interviewers can adapt their questions based on the responses
received, exploring unexpected areas and uncovering hidden issues.
​ Disadvantages:
● Time-Consuming: Conducting interviews can be time-consuming,
especially when dealing with multiple stakeholders. Scheduling and
conducting interviews may pose logistical challenges.
● Subjectivity: The information gathered through interviews may be
influenced by the interviewee's biases, opinions, or selective memory,
leading to potential subjectivity.
● Resource Intensive: Interviews require skilled interviewers, and analyzing
the collected data can be resource-intensive.
​ Document Analysis:
Advantages:
 ● Historical Perspective: Examining existing documents provides a historical
perspective on the system or process. It helps in understanding how
things have evolved over time.
● Cost-Effective: Document analysis is generally less resource-intensive
compared to interviews. It allows analysts to gather information without
the need for direct interaction with stakeholders.
● Objective Data: Documents, if well-maintained, can provide objective and
factual information. They serve as a valuable source for understanding
rules, regulations, and existing procedures.
​ Disadvantages:
● Outdated Information: Documents may become outdated, and reliance on
obsolete or inaccurate documents can lead to misinformation.
● Incomplete Information: Documents may not always provide a complete
picture of a system or process, and crucial details might be missing.
● Lack of Clarification: Unlike interviews, document analysis does not allow
for real-time clarification of ambiguous or unclear information. Analysts
must interpret the documents without the opportunity to seek immediate
clarification.

In summary, interviews and document analysis are two valuable fact-finding techniques,
each with its own set of advantages and disadvantages. The choice between these
techniques often depends on the specific goals of the analysis, the nature of the
information needed, and the available resources.

3. Describe in detail about form driven methodology.

ANS

Form-Driven Approach in System Development:

A form-driven approach in system development typically involves the design and

development of user interfaces (UIs) or forms that users interact with to input or retrieve
information. This approach is common in various applications, including web
development, database systems, and business software. Here's an overview of the key
aspects:

​ Requirements Gathering:
● Understand the data and information that users need to input or retrieve
through the forms. Identify the necessary fields, data validation rules, and
user interactions.
 ​ Form Design:
● Design the user interface or forms based on the gathered requirements.
This includes determining the layout, organization of fields, input controls,
and any supporting elements such as buttons, labels, or help text.
​ Data Validation:
● Implement validation mechanisms within the forms to ensure that users
enter correct and valid data. This can include checks for data types, range
validation, and consistency checks.
​ User Interaction:
● Define how users will interact with the forms. Consider usability aspects,
such as navigation between fields, error handling, and feedback
mechanisms to guide users through the input process.
​ Integration with Backend:
● Connect the forms to the backend system or database where the entered
data is processed, stored, or retrieved. Ensure that there is a seamless
flow of data between the user interface and the underlying system.
​ Testing:
● Conduct thorough testing of the forms to identify and address any issues
related to data validation, user interaction, and integration with the
backend. This includes both functional and usability testing.
​ Iterative Refinement:
● Gather feedback from users and stakeholders, and use it to iteratively
refine and improve the forms. This process may involve making
adjustments to the layout, adding or removing fields, or enhancing user
guidance.

Advantages:

● User-Friendly: Form-driven approaches often result in user-friendly interfaces, as

users interact with a structured and familiar format.
● Efficient Data Entry: Users can input information quickly and accurately through
well-designed forms.
● Consistency: Standardized forms contribute to data consistency and reduce the
likelihood of errors.

Disadvantages:

● Rigidity: Form-driven approaches can be rigid, and changes may be challenging

to implement once a system is in place.
 ● Limited Flexibility: Users may find it challenging to input information that doesn't
fit neatly into the predefined form structure.
● Dependency on Design: The effectiveness of the approach depends heavily on
the initial design of the forms.

4. What are the types of files used in an organization?

ANS

In an organization, various types of files are used to manage and store information
efficiently. These files serve different purposes and are used by individuals and
departments across the organization. Here are some common types of files used in
organizations:

​ Text Documents:
● Description: These are basic documents that contain textual information.
They can include memos, letters, reports, and other written
communication.
● File Types: Common file types for text documents include .docx (Microsoft
Word), .pdf (Portable Document Format), and .txt (plain text).
​ Spreadsheets:
● Description: Spreadsheets are used for organizing and analyzing
numerical data. They can be used for budgeting, financial analysis, and
various types of data tracking.
● File Types: Common file types include .xlsx (Microsoft Excel), .csv
(Comma-Separated Values), and .ods (OpenDocument Spreadsheet).
​ Presentations:
● Description: Presentation files are used for creating slideshows to convey
information visually. They are often used in meetings, seminars, and
conferences.
● File Types: Common file types include .pptx (Microsoft PowerPoint) and
.pdf (Portable Document Format).
​ Images and Graphics:
● Description: These files store visual content, such as photographs,
diagrams, charts, and other graphical elements.
● File Types: Image file formats include .jpg, .png, .gif, and .svg, while
graphic design files may include formats like .ai (Adobe Illustrator) and
.psd (Adobe Photoshop).
 ​ Databases:
● Description: Database files store structured data and are used for efficient
data management. They can include customer databases, employee
databases, and other structured information.
● File Types: Common database file formats include .accdb (Microsoft
Access), .sqlite, and .db (generic database file).
​ PDFs (Portable Document Format):
● Description: PDFs are used for creating documents that preserve the
layout and formatting across different platforms. They are commonly used
for sharing documents.
● File Types: .pdf (Portable Document Format).
​ Emails:
● Description: Emails are electronic messages used for communication
within and outside the organization.
● File Types: Emails are often stored in .pst (Personal Storage Table) or
.mbox (Mailbox) formats.
​ Audio Files:
● Description: Audio files store sound recordings and are used for various
purposes, such as meeting recordings or voice memos.
● File Types: Common audio file formats include .mp3, .wav, and .ogg.
​ Video Files:
● Description: Video files store moving images and are used for
presentations, training, and other visual communication.
● File Types: Common video file formats include .mp4, .avi, and .mov.
​ Archives and Compressed Files:
● Description: These files contain one or more files or directories that have
been reduced in size for storage or transmission purposes.
● File Types: Common compressed file formats include .zip, .rar, and .tar.

These are just some of the types of files used in organizations, and the specific types
may vary based on the nature of the organization and its activities. Effective file
management is crucial for maintaining organization-wide information flow and
accessibility.

5. Write short notes on conversion plan.

ANS
A conversion plan is a crucial component in the process of implementing a new system
or technology within an organization. It outlines the strategies and steps required to
transition from an existing system to a new one. The conversion process aims to
minimize disruptions, ensure a smooth transition, and maximize the benefits of the new
system. Here are key points to consider when developing a conversion plan:

​ Phases of Conversion:
● The conversion plan typically involves multiple phases. These may include
a pilot phase, where the new system is tested on a smaller scale; a parallel
run, where the old and new systems operate simultaneously for
comparison; and a cutover phase, where the organization fully transitions
to the new system.
​ Data Migration:
● The plan should address how existing data will be migrated to the new
system. This includes ensuring data accuracy, completeness, and integrity
during the transfer process.
​ Training and Education:
● Training is a critical element in the conversion plan. It should outline how
employees will be educated on using the new system. Training programs
may include workshops, tutorials, or user manuals to familiarize users
with the features and functionalities of the new system.
​ Testing Procedures:
● The plan should define the testing procedures to validate the functionality
and performance of the new system. This may involve user acceptance
testing (UAT) and system integration testing (SIT) to ensure that the new
system meets organizational requirements.
​ Communication Strategy:
● Effective communication is essential during the conversion process. The
plan should detail how communication will be handled, both internally and
externally, to inform stakeholders, employees, and customers about the
changes, timelines, and potential impacts.
​ Contingency Plans:
● Contingency plans are essential in case unexpected issues arise during
the conversion. The plan should outline strategies for addressing
unforeseen challenges and minimizing the impact on daily operations.
​ Timeline and Milestones:
● The conversion plan should include a detailed timeline with specific
milestones. This helps in tracking progress and ensures that the
implementation stays on schedule.
 ​ User Support:
● Consideration should be given to providing adequate user support during
and after the conversion. This may involve a help desk, support personnel,
or online resources to assist users with any issues they may encounter.
​ Monitoring and Evaluation:
● The plan should include mechanisms for monitoring the performance of
the new system after implementation. This allows the organization to
identify areas for improvement and ensure that the system aligns with the
intended goals.
​ Documentation:
● Comprehensive documentation is crucial for a successful conversion.
This includes documenting procedures, configurations, and any changes
made during the implementation. It serves as a reference for future
troubleshooting and system maintenance.

In summary, a conversion plan is a detailed roadmap that guides an organization

through the process of transitioning from an old system to a new one. It addresses
various aspects, including data migration, training, testing, communication, and support,
to ensure a successful and smooth implementation.
 B.C.A
Sixth Semester
Sub. Code: 10163
VISUAL BASIC PROGRAMMING
Answer ALL the questions, choosing either (a) or (b).
1. (a) Write a note on Event driven procedures.
Or
(b) How to make an EXE file? Explain with an example.

2. (a) Explain the various data types of Visual Basic.

Or
(b) Discuss the uses of VB controls.
3. (a) Explain any five numeric functions with example.
Or
(b) Write a note on Event handling in VB.

4. (a) Discuss the process of creating menus and adding code.

Or
(b) Write a note on MDI Child forms.

5. (a) Explain about DAO and its properties.

Or
(b) Compare the characteristics of DAO and ADO.