Beruflich Dokumente
Kultur Dokumente
Learner declaration
I certify that the work submitted for this assignment is my own and research sources are fully
acknowledged.
pg. 1 OB0719A37A
Tapan sandha
Contents
PROJECT REPORT-2:......................................................................................................................3
A. Project background:................................................................................................................3
B. Project Objective:....................................................................................................................3
C. Project Requirement:.................................................................................................................4
1.undertake a software development lifecycle:....................................................................................5
A. software investigation to meet a business need:..........................................................................5
B. Software analysis tools/techniques:............................................................................................7
a. Techniques used in project:...............................................................................................................7
b. Tools used in project:....................................................................................................................7
C. Software requirement traceability................................................................................................9
a. Define Traceability:........................................................................................................................9
b. Requirement:.................................................................................................................................9
D. Two approaches to improving software quality:......................................................................11
a. Two improving steps:...................................................................................................................11
b. Test Cases:...................................................................................................................................13
E. Function design paradigm can improve software quality:.......................................................14
a. CRUD Define:...............................................................................................................................14
2.suitability of software behavioural design techniques.....................................................................15
a. Define software behavioural:.......................................................................................................15
B. Two software behavioural specification methods....................................................................17
a. Flow chart technique...................................................................................................................17
b. pseudo Code:...............................................................................................................................18
C. Differentiate finite state machine (FSM) and an extended-FSM...........................................19
a. FSM..............................................................................................................................................19
b. EFSM............................................................................................................................................20
D. Data driven software improve the reliability and effectiveness:......................................21
a. Data-driven define:..................................................................................................................21
b. there are two types of data:........................................................................................................21
TECHNICAL DOCUMENT:.............................................................................................................23
MANUAL DOCUMENT:...................................................................................................................26
a. Home page:..................................................................................................................................26
b. Courses page:..........................................................................................................................26
c. Register page:..............................................................................................................................27
BIBLIOGRAPHY:....................................................................................................................................28
pg. 2 OB0719A37A
Tapan sandha
PROJECT REPORT-2:
A. Project background:
pg. 3 OB0719A37A
Tapan sandha
C. Project Requirement:
pg. 4 OB0719A37A
Tapan sandha
1.undertake a software development lifecycle :
A. software investigation to meet a business need:
pg. 5 OB0719A37A
Tapan sandha
8. Also, the backend can be done by PHP as well but the client wants it in
JSP so PHP’s not an option here.
9. MySQL is extremely important to host and store
student’s data submitted via the registration form in the database.
pg. 6 OB0719A37A
Tapan sandha
B. Software analysis tools/techniques:
5.Jsp used for server-side scripting to connect the website to the database.
pg. 7 OB0719A37A
Tapan sandha
3.Filezilla.
pg. 8 OB0719A37A
Tapan sandha
C. Software requirement traceability
a. Define Traceability:
b. Requirement:
pg. 9 OB0719A37A
Tapan sandha
Two screen-shot:
Registration Form:
pg. 10 OB0719A37A
Tapan sandha
D. Two approaches to improving software quality:
1.To improve software quality, it is absolutely paramount to Test early and Test
often.
Early testing will ensure that any defects do not snowball into larger, more
complicated issues.
2.The bigger the defect, the more expensive it becomes to iron out
any issues.
3.The earlier you get your testers involved, the better.
4.It is recommended to involve testers early in the software design process to ensure
that they remain on top of any problems or bugs as they crop up, and before the
issues grow exponentially which takes it harder to debug.
5.Testing often requires a focus on early adoption of the right automated testing
discipline.
6. Start by automating non-UI tests initially then slowly increasing coverage to UI
based tests when the product stabilises. If your application utilises Web services.
7.This is an important time to work with your software developers to ensure
automated.
8.testing is also introduced to your development teams, increasing testing coverage,
accuracy and improving quality of the overall product.
9.A study published in the Journal of Information Technology.
10.Management has revealed that the cost to rectify a bug increases roughly 10
times with each passing stage of development.
pg. 11 OB0719A37A
Tapan sandha
B. Implement quality controls from the beginning:
1.Testers can monitor quality controls and create awareness in partnership with
developers to ensure standards are continually being met.
2.Quality control starts from the beginning, which is an ongoing process throughout
the delivery.
3.A good relationship between testers and developers can help the project software
strategy develop effectively.
4.A systematic methodology in quality control can ensure that coding errors and
bugs are dealt with effectively, following a structured process.
pg. 12 OB0719A37A
Tapan sandha
b. Test Cases:
SR.N TEST CASE EXPECTED ACTUALL PASS/FAIL Comment
O RESULT RESULT
1. When tested The Alert pop- The Alert pass I leave any box
registration form alert. ups shown. pop-ups. in register form,
then alert
1. Go to
shown and not
Registration
submitted your
page.
form.
2. Filled form, if
any box empty
leave then
show alert.
pg. 13 OB0719A37A
Tapan sandha
E. Function design paradigm can improve software quality:
a. CRUD Define:
pg. 14 OB0719A37A
Tapan sandha
2.suitability of software behavioural design techniques.
1.To achieve its underlying business requirements, the software project must capture
the tasks/actions that the users will need to perform.
2.User requirements provide this level of project scope and focus: they provide
the” for the software project.
3.The user requirements address the tasks that can be performed and their expected
outcomes.
pg. 15 OB0719A37A
Tapan sandha
C. Functional Requirements:
1.The user-level experience may need to be described in terms of what the
developer
is supposed to build. This task falls to functional requirements: they too provide
the information for the software project, but in detailed terms relevant to a
developer.
2.For example, a functional requirement might be: “The system shall
require an approving manager to select one of three approval decision options:
Approve, Disapprove, Defer.”
3.The primary audiences for functional requirements are developers and testers.
4.As a recommended good practice, each functional requirement should be
accompanied by a test case that can be used to unambiguously verify if that
requirement has been met.
pg. 16 OB0719A37A
Tapan sandha
B. Two software behavioural specification methods
pg. 17 OB0719A37A
Tapan sandha
b. pseudo Code:
START:
ELSE
When form submitted, all user values stored in database.
ENDIF
ELSE
In Display error show.
End if
END.
pg. 18 OB0719A37A
Tapan sandha
C. Differentiate finite state machine (FSM) and an extended-FSM
a. FSM
1.An FSM always performs a transition on a given input from one state to another.
2.The finite state machine has less computational power than some other models of
computation such as:
Then, let us consider a more complex example which is taken from a real project.
There is a new user registration scenario. New user goes through several steps
during registration:
2. E-mail confirmation;
4. Registration completion.
One may notice that the implementations suffer from some drawbacks:
pg. 19 OB0719A37A
Tapan sandha
3. As the time goes by, implementations get spread over the project, which in
turn can lead to errors.
b. EFSM
1.In EFSM however only performs a transition when a given set of conditions have
been satisfied.
2.An EFSM allows you to also use variables for example you could implement a for
loop.
3.This allows you to easily model algorithms that would otherwise require a
combinatorial explosion of states.
1.Thus, their satisfaction and the non-detection of defects, offers a greater quality
and reliability indication for the tested software.
2.The EFSM-based criteria are complementary to the structural testing criteria from
which they were derived.
pg. 20 OB0719A37A
Tapan sandha
D. Data driven software improve the reliability and effectiveness:
a. Data-driven define:
Data driven programming is a programming model where the data itself
controls the flow of the program and not the program logic. It is a model where
you control the flow by offering different data sets to the program where the
program logic is some generic form of flow or of state-changes.
b. there are two types of data:
you things like how many visitors your site received, how long they stayed, and
1.All data is not created equal. To actually do something with your data, it needs
to be good quality.
2.What is good quality data in this context? Empirical data. 3.Empirical data is
data that’s been gathered through intentional and rigorous observation and
experimentation.
4.The best empirical data sets out to answer a specific question or to address
particular problem.
pg. 21 OB0719A37A
Tapan sandha
c. Putting that Data to Use: Data-Driven Design:
1.The nice thing about using data to drive design is that it gives you more
information about what works and what falls flat.
2.Often in the design process, gut feelings and personal preference can take
priority over rational design decision making.
3.If you’ve got both quantitative and qualitative data to back up your design
choices, in theory the best decision should be obvious.
4.The better the data you’ve collected, the better the decisions you can make (to
a point).
d. It lets you track changes over time:
1.Whenever you make a change to your site’s design, you don’t want it to be a
shot in the dark.
2.Collecting data after you do something like changing a design.
3.feature will tell you whether the changes you’ve made are working, and it’ll help
you understand better what your users respond to and what they don’t.
pg. 22 OB0719A37A
Tapan sandha
TECHNICAL DOCUMENT:
1.
2.
pg. 23 OB0719A37A
Tapan sandha
3.
4.
1. String qry
Query String is a collection is used to retrieve the variable values in the HTTP query
string.
A query string is an array of parameters sent to a web page.
2. out.print("Database is successfully inserted Thank you! ")
It is used mostly to print messages to the console. out is an instance of Print-
Stream, which is a public and static member of the class System. As all instances of
Print-Stream class have a public method println(), hence we can invoke the same
on out as well.
pg. 24 OB0719A37A
Tapan sandha
5.
conn=(Connection)DriverManager.getConnection
The getConnection(String url) method of Java DriverManager class attempts to
establish a connection to the database by using the given database URL. The
appropriate driver from the set of registered JDBC drivers is selected.
pg. 25 OB0719A37A
Tapan sandha
MANUAL DOCUMENT:
a. Home page:
b. Courses page:
1. HTML, Java-script, .Net and MS-Office courses will be provided which user can be
access.
pg. 26 OB0719A37A
Tapan sandha
c. Register page:
1. In this page when user filled data and click on submit button all input data stored
in company.
2. Companies use registration forms to sign up customers for subscriptions,
services, or other programs or plans.
pg. 27 OB0719A37A
Tapan sandha
BIBLIOGRAPHY:
pg. 28 OB0719A37A
Tapan sandha