预考考卷 (2013 - 2020)
2013
2014
2015
2016
2017
2018
2019
2020
*以上试卷纯属分享给学弟学妹们，不允许翻印作为商业用途，谢谢！
Wednesday, 2 December 2020
2020 SPM华文预考考卷
预考考卷 (2020)
Johor
Kedah
Kelantan
Kuala Lumpur & Putrajaya
Melaka
Negeri Sembilan
Pahang
Penang
Perak
Perlis
Sabah
Sarawak
Selangor
Terengganu
Others
*以上试卷纯属分享给学弟学妹们，不允许翻印作为商业用途，谢谢！
2019 SPM华文预考考卷
预考考卷 (2019)
Johor
Kedah
Kuala Lumpur
Melaka
Negeri Sembilan
Pahang
Penang
Perak
Perlis
Sabah
Sarawak
Selangor
Terengganu
Others
A B C D
*以上试卷纯属分享给学弟学妹们，不允许翻印作为商业用途，谢谢！
Monday, 6 April 2020
Maintenance Phase
Software Evolution
- The process of developing software initially, then timely updating it
for various reasons
Purpose: 1) Add more features or to remove absolute functionalities
2)
New requirements and the environment changed
3)
Improve the performance or reliability of the system
Five stages
Stages
|
Explanation
|
Change requests
|
- Urgent changes
may have to be implemented without going through all stages of the software
engineering process
|
Impact Analysis
|
- A formal way
of collecting data and supposition in support of the pros and cons in any
change or disruption to your system
|
Release planning
|
- Fault repair
- Platform
Adaptation
- System
enhancement
|
Change
Implementation
|
- Proposed
changes
- Requirements
analysis
- Requirement
updating (if requirements are accepted)
- Software
development
|
System Release
|
- Release the
system and move to maintenance stage
|
Maintenance
- Provide ongoing
assistance for an information system and its users after system is implemented
Objective
- Correct errors
or faults or problems in the system
- Improve system
performance
- Adapt the system
to a changed environment
- Access system
security to prevent future breakdowns
Types of
maintenance
A) Corrective
Maintenance
B) Perfective
Maintenance
C) Preventive
Maintenance
Main Activities
- Tracking
modification requests and error reports
- Monitoring
system performance and improving performance or increase capacity
- Upgrading
hardware and system software
- Improve the
security of the system
- Implementing
changes
- Updating
documentation to reflect changes
If you have any comments, please leave them below!
Don't forget to follow me and share! Thank you!
Implementation Phase
Purpose
- Aim to create
database using database software by system developers than provide training to
the user after system installed and construct the new or modified system and
then deliver it to use
Activities
I) Coding
- For translating system design and writing
program code for every module
- example: Structured Programming, Functional
Programming
Structured
Programming
- encourages the
developer to use subroutines and loops instead of using simple jumps in the
code, thereby bringing clarity in the code and improving its efficiency and
reduce coding time and organize code properly
Functional
Programming
- provides means of computation as
mathematical functions, which produces results irrespective of program state
Types of errors
|
1) Syntax error
|
- Errors due to
the fact the syntax of the language is not respected
|
|
2) Logical error
|
- Errors due to
the fact that the specification is not respected
|
|
3) Semantic
error
|
- Errors due to
an improper use of program statements
|
|
4) Compile time
error
|
- Syntax errors
and static semantic errors indicated by the compiler
|
|
5) Runtime error
|
- Dynamic
semantic errors, and logical errors, that cannot be detected by a compiler
|
II) Testing
- to detect only
errors that still appear in the system
Testing
Approaches
A) Functionality
testing
- being tested
without taking the actual implementation in concern
Equivalence
class
- The input is
divided into similar classes. If one element of a class passes the test, it is assumed
that all the class is passed.
Boundary values
- The input is
divided into higher and lower end values. If these values pass the test, it is
assumed that all values in between may pass too.
Cause-effect
graphing
- A testing
technique where combinations of input values are tested in a systematic way.
Pair-wise
Testing
- The behavior of
software depends on multiple parameters. In pairwise testing, the multiple
parameters are tested pair-wise for their different values.
State-based
testing
- The system
changes state on provision of input. These systems are tested based on their
states and input.
B) Implementation
testing
- Testing the
functionality and the way it is implemented is also analyzed
Control-flow
testing
- The purpose of
the control-flow testing to set up test cases which covers all statements and
branch conditions. The branch conditions are tested for both being true and
false, so that all statements can be covered.
Data-flow
testing
- This testing
technique emphasis to cover all the data variables included in the program. It
tests where the variables were declared and defined and where they were used or
changed.
Testing Level
|
1) Unit Test
|
- verifies that
each individual program or object work by itself
|
|
2) System Test
|
- verifies that
all program in an application work together properly
|
|
3) Acceptance
Test
|
- Checks the new
system to ensure that it works with actual data
|
|
4) Integration
Test
|
- verifies that
an application works with other application
|
III) Installation
- The specific
system is ready for installation after the database is designed and every
modules code are written and test successfully
IV) Documentation
- Comprehensive
approach of training
- It provides
solution for system users for any trouble shooting
V) Support
- Provide
assistant to solve unexpected problems that fail to overcome by the system
users or operations
VI) Training
- Ready to train
the users to use or manage the system after system installed completely
- Types of training
|
A) In-house
Training
|
- Trainers can
customize running modules to accommodate the immediate needs of company
|
|
B) Online
Training
|
- Offer
convenience because employees can access the training modules at any time
|
|
C)Training Video
|
- Cost-effective
way to offer employee training
|
VII) Data
Conversion
- To convert the
data from an old system to a new system
Direct
Conversion Approach
- Users direct
using the new system on a certain time
Parallel Conversion
Approach
- Operates the old system parallel with the
new system for a period of time. Results from both systems are compared. Users
must work fully in both systems to reap the benefits of a parallel conversion.
This causes it is least risky but the most expensive approach compared to
others.
Phased Conversion Approach
- Implements
subsystems of the new system gradually over a period of time or, alternatively,
the system is implemented in only a few departments, branch officers, or plant
locations at a time
Pilot
Conversion Approach
- implements the new system in one location
in the organization, this means the new system is used and modified at this
test site until the systems analyst believes the system can be successfully
implemented.
If you have any comments, please leave them below!
Don't forget to follow me and share! Thank you!
Sunday, 5 April 2020
Design Phase
Purpose
Process of creating a design for a database that will support the enterprise’s mission statement and mission objectives for the required database system
Activities
- Acquire hardware and software
- Develop the details of the new or modified information system
1) Acquire hardware and software
- Identify technical specifications
- Request Vendor proposal
- Test and evaluate vendor proposals
- Make a decision
2) Develop the details of the new or modified information system
A) Conceptual Database Design
- It involved design rules and technique which explain the whole system simple and easily
- So, it reduces the time spent and energy needed for coding, debugging and maintenance
- Conceptual data model is source of information for logical design phase
B) Logical Design
- A process of developing information that going to be applied by organization based on a data model
- Conceptual data model is refined and mapped on to a logical data model
Three main activities
- Production of conceptual data model for all users
- Production of logical data model for every user
- Production of global logical data model
C)Physical Design
- Process of producing a description of the database implementation on secondary storage
Activities
- Determination hardware specifications for database server and peripheral devices
- Determination software specification for operating system (Linux) and special software (e.g. Java)
- Design user interface and data captures devices such as keyboard and mouse
- Report format such as summary report
Application Design
- Design of user interface and application programs that use and process the database.
- Includes two important activities:
1) Transaction
Design
- An action, or series of actions, carried out by a single user or
application program, which accesses or changes content of the database.
- Three main types of transactions: retrieval, update, and mixed
2) User Interface Design
- By
prototyping, it is used to identify features of a system that work well, or are
inadequate and clarify the users’ requirements
Software Design
Design
|
Explanation
|
1) Architectural design
|
Identify the overall structure of the system,
the principal components (sometimes called sub-systems or modules), their
relationships and how they are distributed.
|
2) Abstract Specification
|
An abstract specification of its services and
the constraints under which it must operate
|
3) Interface design
|
Define the interface between system
components
|
4) Component design
|
Take each system component and design how it
will operate
|
5) Data structure design
|
Design the system data structures and how
these are to be represented in a database or structure
|
6) Algorithm design
|
Design or formulate a formula in design
|
6
basic software models
-
Waterfall Model
- V-shaped
Model
- Iterative Model
- Spiral
Model
- Big
Bang Model
-
Agile Model
For more details: https://www.roberthalf.com.au/blog/employers/6-basic-sdlc-methodologies-which-one-best
If you have any comments, please leave them below!
Don't forget to follow me and share! Thank you!
Friday, 3 April 2020
Analysis Phase
Purpose
- To understand the detail study on the current system to identify the new requirement
- To understand the detail study on the current system to identify the new requirement
Activities
1) Conduct a preliminary investigation
- A general study of the project conducted by system analyst. Then, present finding report
- If the project team committee approves, then detail analysis begins
More details: Preliminary Investigation
More details: Preliminary Investigation
2) Perform Detail Analysis
- Study how the current system work, determine the users’ needs and requirements and recommend a solution
- Method to obtain user’s requirement
I. Document review
iii. Interview
iv. Sampling
Structure of System Requirement
Purpose
- To get the information about the detained function and operations needed in the system development process
- to get the accurate and timely data and information in the system development process
- to help system analyst to understand exactly how the current system work before developing a new system
Types of modelling in Structure of System Requirement
- Process modelling
- Conceptual data modelling
Hot Question: Why involve users in system development process
Answer: Users are people who use the system and they provide information about the detailed function and operations needed in the system development process. Besides that, users are also easier to accept the system if they involve in a system development process.
If you have any comments, please leave them below!
Don't forget to follow me and share! Thank you!
Subscribe to:
Posts (Atom)