Sie sind auf Seite 1von 28

Assessment Brief - 2

Student Name/ID Number: Tapan sandha(OB0719A37A)


Unit Number and Title: Unit 9 Software Development Cycles
Academic Year: 2019-2020
Unit Assessor: Jeyashree Rajkumar.
Development of Registration Form for a Training
Assignment Title:
Organization – Part 2
Issue Date: 4th November, 2019
Submission Date: 7th November, 2019
Internal Verifier Name: Pramod sir.
Date: 4-11-2019

Learner declaration

I certify that the work submitted for this assignment is my own and research sources are fully
acknowledged.

Student signature: Date: 4-11-2019

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:

This project gives us an opportunity to demonstrate our capabilities in the following


areas:
• Evaluating various SDLC models and selecting the appropriate one for this
assignment.
• Conducting Feasibility Analysis.
• Using Software Behavioural design techniques.
• Developing Java Classes for the solution.
• Executing the test cases and validating that the form meets the requirements.
• Ensuring that the requirements are met by the software implementation.
B. Project Objective:

‘ABC Learning Centre’ is an IT Training institute that conducts courses like


‘Programming in Java’, ‘Programming in .Net’, ‘Microsoft Office’, ‘HTML’ etc.
As a Website Developer, we have been approached by ‘ABC Learning
Centre’ to develop an Online Student Registration Form for their institution. The
institution intends to capture student’s details at the time of enrolment in an online
application developed in JSP and MySQL.
As part of the assignment we are expected to do the following tasks.
 To design the Student Registration form along with the database.
 To develop the registration form using HTML, JavaScript and JSP.
 To test the registration form before releasing to users as per the Test Scripts.
 We have created for Testing.
 To prepare a technical document and a user manual.

pg. 3 OB0719A37A
Tapan sandha
C. Project Requirement:

1. Student First Name is a mandatory field.


2. Student Last Name is not a mandatory field.
3. For Gender field you will provide option button with two options as Male and
Female.
4. Residential Address is a Text area field and is used to capture student
address.
5. Phone No is a numeric field and the length of Phone number should be
maximum 11 characters.
6. List of courses offered should be shown in a dropdown box from where
student has to select a course of his/her choice.
7. Create the appropriate tables in database.

pg. 4 OB0719A37A
Tapan sandha
1.undertake a software development lifecycle :
A. software investigation to meet a business need:

While undertaking a software investigation to meet a business need, we came


across ‘ABC Learning Centre’.
‘ABC Learning Centre’ is an IT Training institute that conducts courses like
‘Programming in Java’, ‘Programming in .Net’, ‘Microsoft Office’, ‘HTML’ etc.
As a Website Developer, we have been approached by ‘ABC Learning
Centre’ to develop an Online Student Registration Form for their institution. The
institution intends to capture student’s details at the time of enrolment in an online
application developed in JSP and MySQL.
As part of the assignment we are expected to do the following tasks.
1.To design the Student Registration form along with the database.
2.To develop the registration form using HTML, JavaScript and JSP.
3.To test the registration form before releasing to users as per the Test Scripts we
have created for Testing.
4.To prepare a technical document and a user manual.
The requirements specified by ABC Learning Centre are listed below:
1. Student’s First Name is a mandatory field.
2. Student’s Last Name is not a mandatory field.
3. For Gender field you will provide option button with two options as Male and
Female.
4. Residential Address is a Text area field and is used to capture student address.
5. Phone No is a numeric field and the length of Phone number should be maximum
11 characters.
6. List of courses offered should be shown in a dropdown box from where student
has to select a course of his/her choice.
7.To meet these Software requirements, Operating Systems like Windows,
Linux or MacOS can be used.
Technologies like JSP is required for backend and HTML to develop the required
registration form also giving a little touch to it by using JavaScript.

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:

a. Techniques used in project:

1. HTML to format text as titles and headings, to arrange graphics on a


webpage, to link to different pages within a website, and to link to different
websites.

2. CSS for styling HTML document.

3.Java-script for various functions and validation.

4.Ajax, php for making the website dynamic.

5.Jsp used for server-side scripting to connect the website to the database.

6. MYSQL as the database.


7. IntelliJ as an IDE.
8. Eclipse also an IDE.

9. There are four basic types of software analysis tools:


 Code Coverage—Measures the amount of the software that has been
executed.
 Instruction Trace—Creates a record of exactly what happens as the code is
executed.
 Memory Analysis—Tracks the code's memory usage and identifies possible
errors.
 Performance Analysis—Identifies performance bottlenecks and other issues.
allowing fine-tuning of the application for higher performance.

b. Tools used in project:


1.Eclipse.

2.Xampp – Apache, My SQL

pg. 7 OB0719A37A
Tapan sandha
3.Filezilla.

pg. 8 OB0719A37A
Tapan sandha
C. Software requirement traceability
a. Define Traceability:

Traceability is the ability to trace something. It is applicable in different fields,


including software development and healthcare. Across industries, traceability is
used to comply with regulations and minimize risk.

b. Requirement:

SR.NO Required CLASS Requirement Technologies


REQUIRED meet
used
MEET
1 Student First Name data. JSP yes html, CSS, java-
script, JSP.
2 Student Last Name data. JSP yes html, CSS, java-
script, JSP.
3 Gender data. JSP yes html, CSS, java-
script, JSP.
4 Residential Address data. JSP yes html, CSS, java-
script, JSP.
5 Phone Number data. JSP yes html, CSS, java-
script, JSP.
6 Course Selected data. JSP yes html, CSS, java-
script, JSP.

pg. 9 OB0719A37A
Tapan sandha
Two screen-shot:

Registration Form:

Registration Form validation:

pg. 10 OB0719A37A
Tapan sandha
D. Two approaches to improving software quality:

a. Two improving steps:


A. Test early and Test often with Automation:

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.

2. Register page clicked Registration page Registration pass In nav bar


on home page. should be page hyper-
display. should reference not
1. Enter website
display. given properly,
address.
then an empty
2. Go to nav bar page will be
and click on open.
register.

pg. 13 OB0719A37A
Tapan sandha
E. Function design paradigm can improve software quality:
a. CRUD Define:

CRUD is basically used in the context of database driven application where it


Creates, Reads, Updates and Deletes the data of database. CRUD is also known as
create, read, update and delete.

pg. 14 OB0719A37A
Tapan sandha
2.suitability of software behavioural design techniques.

a. Define software behavioural:

The Behavioural Model bases the gathered requirements on user interactions with


the system (represented as use cases which we'll talk about in the next section)
instead of formulas, rules, and process flow (which are functional in nature). This is
an important distinction because it shifts the focus of the requirements from the
operations the software can perform, when operating the system.
A. Business Requirements:
1.Software projects are undertaken to satisfy some organization-defined set of
needs.
2. These needs are articulated in the form of business requirements.
3. Business requirements lay out the anticipated value or benefit that
the organization and its serviced community expect to receive from the software
project. 
4. For example, business requirements might address a software vendor’s
goal of providing a readily-accessible, secure means for a government contractor to
perform, document and manage procurement system compliance reviews.
5.Business requirements are typically documented in organization vision and scope,
project charter, business case, or marketing requirements documents.
B. User Requirements:

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

a. Flow chart technique

pg. 17 OB0719A37A
Tapan sandha
b. pseudo Code:

All pseudo code written according to above flow chart:

START:

Registration form Display.


If Input from users
          
                Then validate form values
      ENDIF

If validation show error


Then user will fill form again.

ELSE
When form submitted, all user values stored in database.
ENDIF

If Values stored in database.

Then, Thankyou message will be display.

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:

1. Filling out a form;

2. E-mail confirmation;

3. Mobile device binding via QR-code;

4. Registration completion.

One may notice that the implementations suffer from some drawbacks:

1. The method must be changed if business-rules change.

2. The code is poorly readable.

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.

4.EFSM Architecture: An EFSM model consists of the following three major


combinational blocks (and a few registers).

 FSM-block: A conventional finite state machine realizing the state transition


graphs of the EFSM model.
 A-block: an arithmetic block for performing the data operation associated with
each transition. The operation of this block is regulated by the output signals of
the FSM block.
 E-block: A block for evaluating the trigger conditions associated with each
transition. The input signals to this block are the data variables, while the output
is a set of binary signals taken for input by the FSM-block.

5.EFSM-Based Criteria Advantages and Disadvantages:

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:

1.Quantitative data is numerical data (such as analytics or statistics) that tells

you things like how many visitors your site received, how long they stayed, and

how they got there

2.Qualitative data is non-numerical data that helps to tell you about.

1.There’s a common misconception that quantitative data is more important or


reliable than qualitative data.
2.Sure, quantitative data is easier to gather (and numbers seem more
‘scientific’), but it’s essentially meaningless without qualitative data.

b. Getting Good Data

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.

<form action="data.jsp" method="get" name="frm" >:


Solution:
1.Action: The purpose of the HTML action attribute is to specify the URL of
a form processor.
2. method="get": The form-data can be sent as a URL-variables.

2.

1. using request.getParameter()method used to recalled in Jsp.


For examples: We create two fields in html page user-id, password and submit
button. In this form we have enter user-id and password which is recalled in JSP
page by using request.getParameter() method of the request object.

pg. 23 OB0719A37A
Tapan sandha
3.

1.Class.forName() for loading driver class of mysql or oracle or any database.


2.Class.forName ("com.mysql.jdbc.Driver"):
The reason is Java was written for achieving platform independence and we do not
want anything to hard code.

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:

1. For a Web site developer, a home page is the first page presented


when a user selects a site or presence on the World Wide Web.
2. In home page all pages nav are given, so you can go any page.
3. Suppose, if you click on registration page then, form page will be open.

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:

Anon., 2017. [Online]


Available at:
https://deepblue.lib.umich.edu/bitstream/handle/2027.42/25196/0000635.pdf;sequen
ce=1
qiutes, b., 2019. [Online]
Available at: https://content.intland.com/blog/alm/benefits-of-requirements-
traceability-in-application-development

TestPoint, 2019. 11 Ways To Improve Software Quality. [Online]


Available at: https://testpoint.com.au/11-ways-to-improve-software-quality/
[Accessed November 2019].

WhatIs.com, 2019. What is a Finite State machine. [Online]


Available at: https://whatis.techtarget.com/definition/finite-state-machine
[Accessed November 2019].

qiutes, b., 2019. [Online]


Available at: https://content.intland.com/blog/alm/benefits-of-requirements-
traceability-in-application-development

technique, t. a., n.d. [Online]


Available at: https://www.gao.gov/assets/200/192021.pdf
[Accessed 2016].

pg. 28 OB0719A37A
Tapan sandha

Das könnte Ihnen auch gefallen