Author Archives: rajurathod003

lab evaluation-5 raju

http://www.4shared.com/office/KBVqCMJ1/Online_shopping.html
http://www.4shared.com/office/93A5wXnK/USers_manual.html

Lab Evaluation 4….Raju

 

 

Online Book Store Test

Baseline test

Baseline:

  1. Stakeholders (Application users) are two identical users, customer and administrator.
  2. Customer shall register their information to the database (ID, password, name, address, phone number, email, credit card number, etc)
  3. The application shall support simple search of books (by ISBN, title and author etc)
  4. User be able to order books (registered user only)
  5. Administrator shall add the inventory list.
  6. Administrator shall delete the inventory list.

Test Number #1

 

Test case

: Stakeholders (Application users) are two identical users, customer and administrator.

 

Test procedure:

  1. Check whether the webpage exists for customer.

Test resultSatisfied

  1. Check whether the webpage separated with one for administrator exists for customer.

Test resultSatisfied

 

Test Number #2

 

Test case

: Customer shall register their information to the database (ID, password, name, address, phone number, email, credit card number, etc)

 

Test procedure:

  1. Move to the webpage for customer. 
  2. Check whether the menu for registration exists or not.

Test resultSatisfied. In the right top part of the webpage

  1. Check whether the menu for registration is linked correctly.

Test resultSatisfied

  1. Check whether the customer be able to register successfully.

Test resultSatisfied.

 

Test Number #3

 

Test case

: The registered customer should be able to search books. (By ISBN, title and author)

 

Test procedure:

  1. Check whether the menu for simple search exists or not.

Test resultSatisfied. In the right top part of the webpage for the customer logged in.

  1. Check whether the menu for search is linked correctly.

Test resultSatisfied.

  1. Check whether the customer be able to search books by ISBN successfully.

Test resultSatisfied.

  1. Check whether the customer be able to search books by title successfully.

Test resultSatisfied.

  1. Check whether the customer be able to search books by author successfully.

Test resultSatisfied.

 

Test Number #4

 

Test case

: The registered customer should be able to order a book.

 

Test procedure:

  1. Check whether the menu for ordering a book exists or not.

Test resultSatisfied. In the right top part of the webpage for the customer logged in.

  1. Check whether the menu for ordering a book is linked correctly.

Test result: Satisfied. 

  1. Check whether the administrator be able to order a book successfully.

Test resultSatisfied.

 

Test Number #5

 

Test case

: Administrator shall add the inventory list

 

Test procedure:

  1. Move to the webpage for administrator 
  2. Check whether the menu for adding and deleting exists or not.

Test resultSatisfied. In the right top part of the webpage

  1. Check whether the menu for adding a book is linked correctly.

Test resultSatisfied

  1. Check whether the administrator be able to add a book successfully.

Test resultSatisfied.

 

Test Number #6

 

Test case

: Administrator shall delete the inventory list

 

Test procedure:

  1. Move to the webpage for administrator
  2. Check whether the menu for deleting exists or not.

Test resultSatisfied. In the right top part of the webpage

  1. Check whether the menu for adding a book is linked correctly.

Test resultSatisfied

  1. Check whether the administrator be able to delete a book successfully.

Test resultSatisfied.

 

 

Lab evaluation3- raju

The Different  programing paradigm applicable for framework ONLINE  Book Store are as fallows

The Different elements of coding standards included in

ONLINE BOOK  STORE are as fallows

1)                  We are including COMMENT LINE(Single /Multiple Comments) ,                                                     which helps for future programmer to   understand source code very easily.

2) We are using PAIR Programing concept here in order to avoid more errors at the time of testing.

3) we are also declaring variables with NAME in order  to avoid name complexity in the Program.

4)we are also using Loop for our frame work in oder to more time to consume while retrieving data.

5)Naming the Accesses functions.

6)Assigning member function Visibility.

The following features identified in design of ONLINE BOOK STORE reliability, compatibility, maintainability, usability, afford ability.

    Reliability: in our ONLINE BOOK STORE  framework we are made it very easy for user to login and for    searching different BOOKS ,

we are providing a search engine to search the different books here the mean time to repair (MTTR) is very small i e in the order of 1000ms

 

compatibility:her  the compatibility means after making some changes to the data base system,will the system  remains same?,

yes which can be done by ADDMINE for updating Books.

 

maintainability: we are maintaining the system from viruses and hacker by implementing with firewall it will not take more time to repair the the system when it fails

usability:usability are usually testing with the help of test case,

afford ability:Since some of the task in this framework are implemented using open source so its cost

afford ability

1)             Object Oriented programing paradigm.

2)Multi Programing Paradigm.

3) Imperative  programing paradigm.

 Object Oriented programing paradigm:

 

since we are using object oriented language for developing framework    of ONLINE BOOK STORE ,             so it includes the Object Oriented Programing paradigm,

we are also using some more languages for developing on line BOOK store i e  we are combining            object oriented paradigm with imperative programing paradigm,

For building ONLINE BOOK STRORE so we are also including  Multiprogramming paradigm.

 

      In Imperative programing paradigm we are actually seeing how the data transferring Between Registers i .e we are analyzing the program in the micro level Thinking   

link

https://github.com/rajurathod/Web-framework-for-online-book-store

task-list1.png

Scrum

The  concept of scrum  was  first time introduced by  Jeff Sutherland

Scrum is an agile method designed to add energy,  focus,  clarity,   and transparency  to the project and implementation. because of this today we are using scrum,  in small,  mid size and large soft ware corporation in all the world.

Scrum is an inspect and adapt approach to continuous quality improvement to a business practices.

Actually scrum has emerged from a rough structure,  for iterative incremental development to a refined,  well structured straight forward framework for complex product development.

Scrum structure development is usually in terms of cycles of work known as sprints these cycles or iterations are less than or equal to one month in length and usually measured in weeks.  these sprints takes place one after the other, these sprints are completes irrespective of work has been completed or not and or never ended hence they are said to be time boxed .

At the beginning of each sprint   a functional team selects items from a list.

They will try to complete at the end of sprint and everyday there is a team meeting for re-planning the work to optimize.

At the end of the sprint they  send  whether customers requirement full filled or not.  and also includes feedback’s  from stake holders.

 

 

This is How Scrum Works

1)The product backlog

Here the scrum project is expressed in the product backlog

The product backlog is a optimized list of what’s required .

2) The  Sprint

Actually this sprint is usually four weeks in length .

The Sprints are of fixed duration and end on a specific date whether

the work has been completed or not  they are never extended.

3 )Sprint Planning

At the beginning of each Sprint,  the Sprint Planning Meeting takes

place.  The Product Owner and Scrum Team (with facilitation from

the Scrum Master) review the Product Backlog,  discuss the goals and

context for the items,  and the Scrum Team selects the items from the

Product Backlog to commit to complete by the end of the Sprint,

starting at the top of the Product Backlog.

Each item selected from the Product Backlog is designed and then

broken down to a set of individual tasks.  The list of tasks is recorded

in a document called the Sprint Backlog.

4 )Daily Scrum Meeting

This is short fifteen minute meeting that happens every work day at a specific time every one on the team should attend this meeting here the progress of the project is analyzed

This information may results in re-planning and further discussion.

5) Sprint Review and Retrospective

After the Sprint ends,  there is the Sprint Review,  where the Scrum team and stakeholder inspect what was done during the Sprint, discuss it,   and figure out what to do next ? .

Present at this meeting are the Product Owner,  Team Members,  and Scrum Master,  plus customers,   stakeholders,   experts,   executives,  and   anyone else interested.

Following the Sprint Review,  the team gets together for the Sprint

Retrospective which is an opportunity for the team to discuss what’s

working and what’s not working,  and agree on changes to try.

Edit This