LAB EVALUATION-1

Here we are using the process model called iterative model

Universal design principles:

  1. Equitable use
  2. Feasibility in use-  highly configurable
  3. Simple and intuitive use
  4. Perceptible info
  5. Tolerance for error
  6. Low physical effort
  7. Size and space for approach and use

Reliability can be defined as the probability that a system performs user required functionality correctly at a framework in given period of time.Reliability largely depends on number of faults in the software- online book store.

Maintainability  refers to the easiness of maintaining a software system.Modification to a system for correction of bugs that are found during the operation.And modification to a system due to environment changes i.e upgrade the system software, e.g. the OS and the database management system.How this term relates to design here? Because to know the bugs in the system by software engineers,they should know how the system works so bugs can be fixed and changes in environment can be adapted.For that Well structured design helps s/w engineers to understand the system.

Affordability referes to cost and time duration of the software system. Cost should be affordable ..

Compatibility means our software should be designed in such a manner that can be used by user efficiently.Like Color, language facility, Options etc..overall design should be user friendly.

Usability means here in online book store we are including some details about the book so user can find the book which he needs?

ImageImageImageImageImage

Edit this entry

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

LAB-Evaluation3- SMITA TANK

https://github.com/SmitaTank/Lab-Evaluation-3–Online-book-store

Image

 

The C# language specification does not define a coding standard. However, the guidelines in this topic are used by Microsoft to develop samples and documentation.

Naming convention:

If you know that a namespace is imported by default in a project, you do not have to fully qualify the names from that namespace.

LAYOUT CONVENTION:

Commenting convention:

// The following declaration creates a query. It does not run 

// the query.

C# follows multi-programming paradigm

Lab Evaluation 3 Khaja Moinuddin

Snippets 

 

Login page

<html>
<body bgcolor=”beige”>
<center>

<jsp:useBean id=”user” class=”obs.User” scope=”session” />

<jsp:setProperty name=”user” property=”*” />

<%
user.login();
if (! user.isLogged())
%>
<h3>Invalid Login. Click <a href=login.html>here</a> to try again! </h3>
<%
else
response.sendRedirect(“home.jsp”);
%>

</center>
</body>
</html>

Registeration page 

<html>
<body bgcolor=”wheat”>
<style>
h3 {font:700 12pt verdana;color:maroon}
a {font:12pt verdana;color:navy}
</style>

<center>

<jsp:useBean id=”user” class=”obs.User” scope=”session” />

<jsp:setProperty name=”user” property=”*” />

<%
String result = user.registerUser();

if ( result == null)
response.sendRedirect(“home.jsp”);
else
out.println(“<h3>Sorry! Registration Failed With Error : <p> ” + result + “</h3> <p> <a href=register.html>Try Again </a> “);

%>

</center>
</body>
</html>

orderitem

 

<jsp:useBean id=”user” scope=”session” class=”obs.User”/>
<%@page import=”java.sql.*”%>

<html>
<style>
a.topic {font:700 11pt verdana;color:white}
td {font:10pt verdana}
th {font:700 10pt verdana;background-color:green;color:white}
</style>

<body bgcolor=”beige”>
<h1>Order Items </h1>

 

<%
String ordid = request.getParameter(“ordid”);
String status = request.getParameter(“status”);

String cmd = “select oi.isbn,title, oi.price,qty, oi.price * qty amount from orderitem oi, books b where b.isbn = oi.isbn and ordid = ” + ordid;

Connection con = user.getConnection();
Statement st = con.createStatement();

ResultSet rs = st.executeQuery(cmd);

%>

<p>

<table width=”100%” cellpadding=2 border=1>
<tr>
<th> ISBN
<th> Title
<th> Price
<th> Quantity
<th> Amount
</tr>

<%
while ( rs.next())
{
%>

<tr>
<td> <%=rs.getInt(1)%>
<td> <%= rs.getString(2)%>
<td> <%= rs.getInt(3)%>
<td> <%= rs.getString(4)%>
<td> <%= rs.getString(5)%>
</tr>

<%
}

rs.close();
st.close();
con.close();

%>

</table>

<p>
<%
if ( status.equals(“n”))
{
%>

<a href=”deleteorder.jsp?ordid=<%=ordid%>”>Cancel This Order</a>
&nbsp;
&nbsp;
<%

}
%>

 

<a href=”javascript:history.back()”>Back </a>

 

 

 

lab evaluation3- manjunath M

lab evaluation 3-vinayak

lab evaluation 3- manjunath

Lab evaluation 3 – Sunny

1)    Programming paradigm applicable to for “Web Framework for online book store”
1)   Objected oriented Paradigms
2)   Multi Programming paradigm

Object Oriented Paradigm (OOP)
OOP is a programming paradigm that uses “objects” – data structures consisting of data fields and methods together with their interactions – to design applications and computer programs. Programming techniques may include features such as data abstraction, encapsulation, modularity, polymorphism, and inheritance.
Some Object Oriented Programming language are JAVA,C++ etc.

Multi Programming Paradigm
Multi programming is a language that supports more than one programming language.
For ex- C# supports both imperative and object oriented features as well as functional programming.
No programming language is enough to develop a project. The idea behind multi programming paradigm is to provide a framework in which programmers can work in a variety of styles. there is an option of  intermixing constructs from different paradigms

2)  Coding standards
**   NAMING CONVENTIONS
Name of variable is in mixed case, starting with lowercase
Global variables starts with “g”.
Class names are in mixed case , starting with uppercase
Class member variables names start with “m_ “
for ex- void Transform(Book book, Writer writer) {
m_book = book;
m_writer = writer;
}
** COMMENTS
Header comment at every function definition is used. This increases code     understandibility
For ex- // This function will add new book to customer cart.
Comments explain WHY instead of HOW.
** Exception classes is suffixed with Exception.

3)
Reliability:
The system shall be available 24 hrs a day and 7 days a week.

Usability
• The system shall support large number of simultaneous users
against the central database at any time.
• The system shall provide access to catalog database with no
more then ten seconds .
• The system must be able to complete 80% of all transactions
within 2 minutes.
Compatibility
The software is compatible with different machine as well as different operating system (Mac,Linux etc.). As there can be variety is user.

Affordability
The Software is developed using coding standards, so there is less cost in maintainence and testing. At the same time user requirements are also fulfilled.

Maintainbility
In case of system failure, system can be restored to previous best know configuration.
New features can also be added with very less changes.

https://github.com/oceanparkk/OnlineBook

Lab evaluation 3 – kishore k

The programming paradigm used for creating the Web framework for online book store is been php, which is an scripting language designed for webdevelopment to produce dynamic webpages. the code is interpreted by a webserver with a php processor module which generates resulting web pages.

elements of coding standard included in this case includes

Single and Double Quotes – Use single and double quotes when appropriate. if we’re not evaluating anything in the string, use single quotes. we should almost never have to escape quotes in a string, because you can just alternate your quoting style,

Indentation -indentation would always reflect logical structure. we Use real tabs and not spaces, as this allows the most flexibility across clients.For associative arrays, values should start on a new line.

Brace Style Braces should be used for multiline blocks in the style. if you have a really long block, consider whether it can be broken into two or more shorter blocks or functions. If you consider such a long block unavoidable, we put a short comment at the end so people can tell at glance what that ending brace ends
Regular Expressions
No Shorthand PHP tags – Many servers have shorthand tags disabled for PHP thus by using full PHP tags is safer and best practice
Naming Conventions -Use of lowercase letters in variable, action and function names

online bookstore system will provide a mechanism for searching the available book title database with various criteria. The system will call attention to books in the inventory that are designated as “special” and will allow users to order books online.

The following features identified in design were implemented- reliability- is accomplished by providing feasible gui to the users and username along with password for purchasing books online,compatibility- is accomplished by designing the software is such a manner such that the user can use it from any browser without any loading problems, maintainability – is accomplished by regular updates in the book store availability so that the customer can get the book that he is seaching for in the net, usability is accomplished by making userfriendly gui’s and easy availability of the books in the internet through the software created, affordability- is provided by providing discounts on the books that is been purchased through online.

This project designs an online bookstore provides a web-based interface. It is the graphical user interface. It have a form for user to input query information to search the database. The users interface then pass the input to the control function, which implemented in Java. The control function is designed to process the input from the users interface, generate the searching query and then gets data from the database and returns to the users interface. The control functions also have bridges to search some external real online bookstores. It can generate the query based on the user input and pass them to the commercial bookstore. The bridge can also handle the response from the commercial bookstore and parse the useful information and display to the user in HTML forms.

link of source code: https://github.com/kishore29/lab-evaluation—3

Lab Evaluation 3 – Smitha

Programming paradigm used:
Object oriented programming paradigm is used in this case as there are many modules to be implemented and involves reusable components such as login module, add/delete/update items to shipping cart.

Coding standards:

(1) There shall be a maximum of 80 characters per line
.
(2) Abbreviations/acronyms shall be mixed case with the first letter upper case and all following letters lower case.
(3) Each variable shall be defined or declared on a separate line.
(4) Use familiar variable names.
(5) Variable names shall be in lowercase.
(6) Local variables (those which are defined within functions) shall be defined before the first line of executable code within a function.
(7) Local variables (those which are defined within a block surrounded by braces) shall be defined before the first line of executable code within a block.
(8) Functions shall explicitly define the return type.
(9) There shall be no space between the function name and the opening parenthesis.
(10)The comment shall appear directly above the line (or block) to be commented for comments describing the methodology or flow of the code.
(11)The comment shall begin at the same indentation as the commented portion.
(12)Comments shall be written in the third person form.
(13)Use nouns to name variables. Ex: username
(14)Use uppercase for words and separate with underscore for naming constants.ex: MAX_VALUE
(15)Do not use names that differ only in case.Ex: theInstance and TheInstance
(16)Use verbs when naming functions.ex: login

Link to sourceforge:
https://sourceforge.net/projects/onlinebkstore/files/?source=navbar

Lab evaluation-3 -Nagaraj

Case study:  Web framework for online book store

Activities

1)      The programming paradigm applicable for the case are

Object  Oriented programming paradigm

Functional oriented Programming paradigm

Multi paradigm programming language

 

2)      The elements of coding standards included in this case

 

 

              Commenting code

        Java Comments

 

Comment Type

Usage

Example

Documentation

 

Starts with /** and ends with */

Used before declarations of interfaces, classes, member functions, and fields to document them.

/**

 * Customer – a person or

 * organization

 */

C style

 

Starts with /* and ends with */

Used to document out lines of code that are no longer applicable. It is helpful in debugging.

 

/*

  This code was commented     out by

*/

 

Single line

 

Starts with // and go until the end of the line

Used internally within member functions to document business logic, sections of code, and declarations of temporary variables.

// If the amount is greater

// than 10 multiply by 100

 

             

 Naming Accessor Member Functions

 

Getters: member functions that return the value of a field / attribute / property of an object.

 

Use prefix “get” to the name of the field / attribute / property if the field in not boolean

Use prefix “is” to the name of the field / attribute / property if the field is Boolean

A viable alternative is to use the prefix ‘has’ or ‘can’ instead of ‘is’ for boolean getters.

 

 

Examples

ex.getMessage();

 

Setters: member functions that modify the values of a field.

 

Use prefix ‘set’ to the name of the field.

 

Example

setMessage();

Member Function Visibility

 

A good design requires minimum coupling between the classes. The general rule is to be as restrictive as possible when setting the visibility of a member function. If member function doesn’t have to be public then make it protected, and if it doesn’t have to be protected than make it private.

 

 

 

 

 

3)

    Maintainability is achieved , ability of the system to undergo changes with a degree of ease. These    changes could impact components, services, features, and interfaces when adding or changing the functionality, fixing errors, and meeting new business requirements.

Usability  can achieved  how well the application meets the requirements of the user and consumer by being intuitive, easy to localize and globalize, providing good access for disabled users, and resulting in a good overall user experience.

Reliability is achieved f a system to remain operational over time. Reliability is measured as the probability that a system will not fail to perform its intended functions over a specified time interval.

 

Note:

      I have used Java programming language, since the java programming language consits of  Object  Oriented programming paradigm ,Functional oriented Programming  paradigm

 .

 

 

 

Case study:  Web framework for online book store

Activities

1)      The programming paradigm applicable for the case are

Object  Oriented programming paradigm

Functional oriented Programming paradigm

Multi paradigm programming language

 

2)      The elements of coding standards included in this case

 

 

              Commenting code

        Java Comments

 

Comment Type

Usage

Example

Documentation

 

Starts with /** and ends with */

Used before declarations of interfaces, classes, member functions, and fields to document them.

/**

 * Customer – a person or

 * organization

 */

C style

 

Starts with /* and ends with */

Used to document out lines of code that are no longer applicable. It is helpful in debugging.

 

/*

  This code was commented     out by

*/

 

Single line

 

Starts with // and go until the end of the line

Used internally within member functions to document business logic, sections of code, and declarations of temporary variables.

// If the amount is greater

// than 10 multiply by 100

 

             

 Naming Accessor Member Functions

 

Getters: member functions that return the value of a field / attribute / property of an object.

 

Use prefix “get” to the name of the field / attribute / property if the field in not boolean

Use prefix “is” to the name of the field / attribute / property if the field is Boolean

A viable alternative is to use the prefix ‘has’ or ‘can’ instead of ‘is’ for boolean getters.

 

 

Examples

ex.getMessage();

 

Setters: member functions that modify the values of a field.

 

Use prefix ‘set’ to the name of the field.

 

Example

setMessage();

Member Function Visibility

 

A good design requires minimum coupling between the classes. The general rule is to be as restrictive as possible when setting the visibility of a member function. If member function doesn’t have to be public then make it protected, and if it doesn’t have to be protected than make it private.

 

 

 

 

 

3)

    Maintainability is achieved , ability of the system to undergo changes with a degree of ease. These    changes could impact components, services, features, and interfaces when adding or changing the functionality, fixing errors, and meeting new business requirements.

Usability  can achieved  how well the application meets the requirements of the user and consumer by being intuitive, easy to localize and globalize, providing good access for disabled users, and resulting in a good overall user experience.

Reliability is achieved f a system to remain operational over time. Reliability is measured as the probability that a system will not fail to perform its intended functions over a specified time interval.

 

Note:

      I have used Java programming language, since the java programming language consits of  Object  Oriented programming paradigm ,Functional oriented Programming  paradigm

 .

 

 

 

Case study:  Web framework for online book store

Activities

1)      The programming paradigm applicable for the case are

Object  Oriented programming paradigm

Functional oriented Programming paradigm

Multi paradigm programming language

 

2)      The elements of coding standards included in this case

 

 

              Commenting code

        Java Comments

 

Comment Type

Usage

Example

Documentation

 

Starts with /** and ends with */

Used before declarations of interfaces, classes, member functions, and fields to document them.

/**

 * Customer – a person or

 * organization

 */

C style

 

Starts with /* and ends with */

Used to document out lines of code that are no longer applicable. It is helpful in debugging.

 

/*

  This code was commented     out by

*/

 

Single line

 

Starts with // and go until the end of the line

Used internally within member functions to document business logic, sections of code, and declarations of temporary variables.

// If the amount is greater

// than 10 multiply by 100

 

             

 Naming Accessor Member Functions

 

Getters: member functions that return the value of a field / attribute / property of an object.

 

Use prefix “get” to the name of the field / attribute / property if the field in not boolean

Use prefix “is” to the name of the field / attribute / property if the field is Boolean

A viable alternative is to use the prefix ‘has’ or ‘can’ instead of ‘is’ for boolean getters.

 

 

Examples

ex.getMessage();

 

Setters: member functions that modify the values of a field.

 

Use prefix ‘set’ to the name of the field.

 

Example

setMessage();

Member Function Visibility

 

A good design requires minimum coupling between the classes. The general rule is to be as restrictive as possible when setting the visibility of a member function. If member function doesn’t have to be public then make it protected, and if it doesn’t have to be protected than make it private.

 

 

 

 

 

3)

    Maintainability is achieved , ability of the system to undergo changes with a degree of ease. These    changes could impact components, services, features, and interfaces when adding or changing the functionality, fixing errors, and meeting new business requirements.

Usability  can achieved  how well the application meets the requirements of the user and consumer by being intuitive, easy to localize and globalize, providing good access for disabled users, and resulting in a good overall user experience.

Reliability is achieved f a system to remain operational over time. Reliability is measured as the probability that a system will not fail to perform its intended functions over a specified time interval.

 

Note:

      I have used Java programming language, since the java programming language consits of  Object  Oriented programming paradigm ,Functional oriented Programming  paradigm

 .

 

 

 Code snippets

.login

   

<html>
<body bgcolor=”beige”>
<center>

<jsp:useBean id=”user” class=”obs.User” scope=”session” />

<jsp:setProperty name=”user” property=”*” />

<%
user.login();
if (! user.isLogged())
%>
<h3>Invalid Login. Click <a href=login.html>here</a> to try again! </h3>
<%
else
response.sendRedirect(“home.jsp”);
%>

</center>
</body>
</html>

Customer:

public class Customer
{

private String custname;
private String password;
private String email;
private String phoneno;

private Context ctx;

public Context getJNDIContext()
{
return ctx;
}

public Customer()
{
ctx = getInitialContext();
}

public void setCustname(String custname)
{ this.custname = custname; }

public String getCustname()
{ return custname; }

public void setPhoneno (String phoneno)
{ this.phoneno = phoneno; }

public String getPhoneno()
{ return phoneno; }

public void setPassword(String password)
{ this.password= password; }

public String getPassword()
{ return password; }

public void setEmail (String email)
{ this.email = email; }

public String getEmail()
{ return email; }

// returns true if uname and pwd are valid
public boolean isValid()
{
Connection con = null;
PreparedStatement ps = null;
try
{
con = getConnection();
ps = con.prepareStatement(“select phoneno, email from customers where custname = ? and pwd= ?”);
ps.setString(1,custname);
ps.setString(2,password);

ResultSet rs = ps.executeQuery();
boolean found = false;

if ( rs.next())
{ phoneno = rs.getString(“phoneno”);
email = rs.getString(“email”);
found = true;
}
return found;
}

CART-

public class Cart
{
ArrayList items = new ArrayList();

public Item find(String isbn)
{
Iterator itr = items.iterator();
Item itm;
while ( itr.hasNext())
{
itm = (Item) itr.next();
if ( itm.getIsbn().equals(isbn))
{
return itm;
}
} // end of while

return null;
}

Link of source code

 

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

lab evaluation -3 anudeep

1)The type of program paradigm used for online web frame work for book store is
object-oriented program paradigm.
The idea of a multiparadigm language is to provide a framework in which programmers
can work in a variety of styles, freely intermixing constructs from different paradigms.
In object-oriented programming, programmers can think of a program as a collection of interacting objects.
it  heps programmer to think on application as a set of concurrent process acting upon logically shared data
So object-oriented is used for online web frame work for book store

2)  Coding standards

 NAMING CONVENTIONS

Name of variable is in mixed case, starting with lowercase

Global variables starts with “g”.

Class names are in mixed case , starting with uppercase

Class member variables names start with “m_ “

for ex- void Transform(Book book, Writer writer) {

m_book = book;

m_writer = writer;

}

COMMENTS

Header comment at every function definition is used. This increases code     understandibility

For ex- // This function will add new book to customer cart.

Comments explain WHY instead of HOW.

 

 

 

 

3)

Reliability:

it will done through online password system

Usability

• The system shall support large number of simultaneous users

against the central database at any time.

Compatibility

The software is compatible with different machine as well as different operating system (Mac,Linux etc.). As there can be variety is user.

Affordability

         the webframe work should be affordable to the user’s.it should be of less cost .since it is online based it is affordable to user’s.

Maintainbility

In case of system failure, system can be restored to previous state.

New features can also be added with very less changes.

LINK FOR 2 ANSWER GITHUB:https://github.com/anudeep345/lab-evaluation–3

Lab evaluation3 by shailesh kumar jha

Generally we use multi programming paradigm to implement  for on line bookstore framework. The language such as Java , c#, python. these all language doesn’t stick to a single programming paradigm but they are the hybrid they uses the concept of different programing paradigm. The idea of a multi paradigm language is to provide a framework in which programmers can work in a variety of styles, freely intermixing constructs from different paradigms.The design goal of such languages is to allow programmers to use the best tool for a job, admitting that no one paradigm solves all problems in the easiest or most efficient way.

Google programing coding standard of JavaScript

1 var:declaration always with var
2constants:
use NAME_LIKE_THIS for constant value
use @const to indicate(non- overwritable) pointer( a variable or     property)
never use the const keyword asit is not supported in internet    explorer
3 semicolons: always use semicolon
4 nested functions : it can be very useful, for example in the creation of continuations and for task of hiding helper function
5 function declaration within a block:never use function declaration within a block as the ECMA doest mainly support scripting language that has got function declaration win a block
6 exception: always try to implement exception handling
7custome exception : yes apply
8 standard features : always prefer non standard feature
9 wrapper objects for primitive types : there is no reason to use wrapper objects for primitive and they are dangerous too.
10 multi- level prototype hierarchies is not referred
11 method and property definition
/** @constructor */ function SomeConstructor() { this.someProperty = 1; } Foo.prototype.someMethod = function() { … };
12 delete : prefer
13 closure : allowed but should be implemented carefully
14 eval() : it can be used only for de serialization
15 with(): with is not allowed
16 this :Only in object constructors, methods, and in setting up closures
17 for -in loop: only for iterating over key in an object
18 associative arrays : never use array as map/hash/associative array
19 multi sting literation : don’t use
20 array and object literals: use Array and Object instead of Array and Object constructor .
21 Modifying prototypes of built in objects :no
22 Internet Explorer’s Conditional Comments : no
23 Naming : in genral use functionNamesLikeThis, variableNamesLikeThis, ClassNamesLikeThis,   EnumNamesLikeThis, methodNamesLikeThis, CONSTANT_VALUES_LIKE_THIS, foo.namespaceNamesLikeThis.bar, and filenameslikethis.js.
24Custom toString() methods: must always succeed without side effect
25 deferred initialization : ok
26 explicit scope : always
27 coding formation : expand for more information
28parentheses only where required
29 strings: preferred
30 JavaScript type: encouraged
31 provide dependencies with goog.provide: only provide top level symbol.
32 compiling: required.

link of github: https://gist.github.com/4602270

lab evaluation 3 – Pooja Pande

  1. Programming parading which can be used in this case is object-oriented. As for the development of the web frame work JAVA will be used and the object oriented programming paradigm supports JAVA well.
  1. Coding standards to be included in this case –

Use full English descriptors that accurately describe the variables/fields/classes. For example,use name like firstName, grandTotal or HelloWorld.

  • Use mixed case to make names readable, class/interface names should be capitalized, first letter of method and variable names should be lower case.
  • Constants should be all capitalized, with underscore to separate the words.
  • Use abbreviations sparsely, but if you do so then use them intelligently. For example, if you want to use a short name for “number”, use like “nbr”, or “num”, document which one you choose for the word “number” and use only that one.
  • Avoid long names (<15 characters is a good idea).
  • Avoid names that are similar or differ only in case
  • Source code structure should be like
    • Beginning comments
    • Package and Import statements
    • Class and interface declarations
  • Wherever appropriate, avoid code that embeds many operations in a single line. 

Link – https://github.com/pooja1110/webframework

Lab evaluation 3 Khaja Moinuddin

  1. identify the programming paradigm applicable for the case?

I think web framework for online book store requires object oriented paradigms.

And I am using jsp for writing server side pages and by default it also uses Servlets.

 

 2 list the elements of coding standards included in this case?

1 Separate class, instance, and local variables.

2 Braces go on their own lines.     

3 Indent at 4 spaces

4 Spaces go around the arguments, not around the keywords

5 Comments must be used not where ever needed

6 Using Javadoc @version

7 Do not use “this”

 3 describe how the following features identified in design were implemented- reliability, compatibility, maintainability, usability, affordability.

Reliability:

                   the server must provide rollback for transactions whenever there is a failure. The system shall be available 24 hrs a day and 7 days a week.

Usability

the system must use web pages that are visible 

The system shall support large number of simultaneous users

against the central database at any time.

Compatibility

                 The software is compatible with different machine as well as different operating system (Mac,Linux etc.). As there can be variety is user.

Affordability

                  The Software is developed using coding standards, so there is less cost in maintainence and testing. At the same time user requirements are also fulfilled.

Maintainbility

                  In case of system failure, system can be restored to previous best know configuration.

New features can also be added with very less changes.

 

the link to github is as follows 

https://github.com/KhajaMoinuddin/web-framework-online-Book-Store-.git

 

Lab evaluation 2 khaja Monuddin

Lab evaluation 2 khaja Monuddin

class diag

Lab evaluation 2 khaja Monuddin

Lab evaluation 2 khaja Monuddin

Activity

Lab evaluation 2 khaja Monuddin

Lab evaluation 2 khaja Monuddin

Sequence diag

Lab evalution-2- Nagaraj

class sequence sequence2. state usecaseonline

 

1)  the relevant software design methodology is spiral model

2)the design princeple is object oriented

3

LAB EVALUATION2- SMITA TANK

Here we are using the process model called iterative model

Universal design principles:

  1. Equitable use
  2. Feasibility in use-  highly configurable
  3. Simple and intuitive use
  4. Perceptible info
  5. Tolerance for error
  6. Low physical effort
  7. Size and space for approach and use

Reliability can be defined as the probability that a system performs user required functionality correctly at a framework in given period of time.Reliability largely depends on number of faults in the software- online book store.

Maintainability  refers to the easiness of maintaining a software system.Modification to a system for correction of bugs that are found during the operation.And modification to a system due to environment changes i.e upgrade the system software, e.g. the OS and the database management system.How this term relates to design here? Because to know the bugs in the system by software engineers,they should know how the system works so bugs can be fixed and changes in environment can be adapted.For that Well structured design helps s/w engineers to understand the system.

Affordability referes to cost and time duration of the software system. Cost should be affordable ..

Compatibility means our software should be designed in such a manner that can be used by user efficiently.Like Color, language facility, Options etc..overall design should be user friendly.

Usability means here in online book store we are including some details about the book so user can find the book which he needs?

ImageImageImageImageImage

Lab evaluation 2 — Pooja pande

1. The software design methodology that cane be used in webframe wrok is spiral as
in here
➢ Significant changes are expected with time.
➢ spiral model is good for larger softwares.
2. The design principles that can be embedded in the design are –
1. Design should be obivous and self-explanatory.
2. Design should be simple. Users are rarely on a site to enjoy the design;
furthermore, in most cases they are looking for the information despitethe
design. Strive for simplicity instead of complexity.
3. approach of guiding users with visually appealing 1-2-3-done-steps, large
buttons with visual effects etc are extremely effective as they lead the visitors
through the site content in a very simple and user-friendly way.
4. Focusing users’ attention to specific areas of the site with a moderate use of
visual elements.
3. The goal of the universal design strategy is to create enabling contexts for all
users. Universal design means designing products and environments for all to the
greatest extent possible, without the need for adaptation or specialized design.
3. Here the user interface is kept simple so that person of any age group can use
the it effictively.
The color of buttons are kept light and normal so that person having problem in
identifying color can even use it . The following princplies should be taken care of –
➢ flexibility
➢ simple and intuitive
➢ size and space for approach and use
4.
➢ Usability – Web usability is an approach to make web sites easy to use for an
end-user, without the requirement that any specialized training be undertaken.
For the same the website is kept simple so that uer can use it without any
problems.
➢ Reliability can be embedded by using 2-3 nameservers and geographically
dispersing them.
➢ Combatibilty – The designed framewrok should be compatible with different
browsers and platforms. For this these points should be taken care of
➢ screen resolution .
➢ frames.
➢ color limitations.pclass dia plogin seq pbooksearch seq pusecase

lab Evaluation 2…Raju

class sate seq usecase

Software Process Model

scrum process model, since requirement keep on changing.

Design principle

Object oriented Programming.

Universal design principles:

  1. Equitable use
  2. Feasibility in use-  highly configurable
  3. Simple and intuitive use
  4. Perceptible info
  5. Tolerance for error
  6. Low physical effort
  7. Size and space for approach and use

lab evaluation 2- Shailesh

user use case classbook use case admistrator

 

reusability of the business logic is greater for the physical layer as this component is developed and tested ,we can use it in any other project and would be helpful for future

Lab Evaluation 2

  1. identify the relevant software Methodology?

Ans. I think object oriented Methodology suits

 

 

  1. List the design Principles that can be embedded in this design ?

Ans  the Following are the design principle

  1.  Cohesion:  Each and every element must be self-sufficient.
  2.         2.  Coupling: we must design this in such a manner that there should be lest amount of                      communication possible.
  3.         3.   Easy to use- this is one of the major features that must be incorporated into this system.
  4.         4.   keep it simple
  5.         5.   Bring objects to life through good visual design.

        6. Always keep your target users in mind as the product is designed.

  1.         7.  Make the interface accessible and visible to users.

        8. Provide the ability to undo and redo actions.

  1.         9.  Maintainable.

        10 reliable.

  1. describe how to embed following features into design – reliability, compatibility, maintainability, usability, affordability.

The transactions between users and the bank for buying of product must be secure

 

The web pages must be platform independent JSP provides platform independence.

 

Follow Coding principles Such as comment indentations  etc. that the people who are going to update or maintain the code must be able to so there work without trouble.

 

Provide Simple user interface so that even a layman can do the transactions.

 

Lab evaluation 2 – kishore k

ImageImageImageImage

Software design methodologythat was used was star uml to accomplish the design of web framework for the online book strore, star UMl is an open source UML tool and it supports most of the diagram types specified.

design principles that can be embedded in the design are we include designing a simple onlineshopping portal. the site will provid a soothing shopping sexperience for customers. the system will allow more han on categories and different brands under the segment. The case will trace the following sequence.

A customer visits the online shopping portal. A customer may but item orjust visit the page and logout. the customer can select a segment to get the different products in the desired brand. the customer can select the product for purchasing. the process can be repeated for more items. once the customer finishes selecting the product the cart can be viewed, if the customer wants to edit the final cart it can be done here. for final payment the customer has to login the portal, if the customer is visiting for the first time he must register with the site, else the customer must use the login page to proceed. final cart is submitted for payment and card details and address are confirmed by the customer is confirmed with a shipment id and delivery of goods

Reliabilty is assured by providing a good framework for the customer while purchasing the product through the online prortal such that online portal perform user required function on a timely basis.

Maintanability in the online portal is assured by providing by providing easy to use framework so that the user can surf the portal without any problems such as correction that is found during the design of the web portal

Affordabality refers to charges on the product that the user can afford for and cost involved in designing the webportal.

compatibility the this framework for the online bookstore had been supported by with efficiency of usage and usability has been provided so that the online portal is userfriendly

 

 

Lab Evaluation 2 – Smitha

1. Design Methodology:

Spiral model can be used as the design methodology for this scenario. This is because spiral is best suited for inventory management related projects and since online book store includes storing huge data related to books and user details risk assessment has to be performed at every phase.

2. Universal Design and design principles:
Equitable Use: The design should not distinguish any group of users. Users from different profession should be able to find books related to their domain. T
Flexibility in Use: The advance search feature helps the user to provide wide range of preferences.
Simple, Intuitive Use: The guidelines provided should not be too technical to understand. They should be easy to understand and to operate.
Perceptible Information: Unnecessary guidelines should not be given. Fields which are self explanatory should not have guidelines provided.
Tolerance for error: Provide high security to prevent publicizing sensitive user information.
Low physical effort: Where ever possible drop down lists should be provided to prevent user from typing effort.

3. Features to be included:

Reliability : The system should provide high reliability by incorporating maximum security features since the user will be providing his account details for shopping purchase all these details should be hidden and should not be accessible to unauthorized person.
Affordability : This can be achieved by making sure that the user is able to get the list of books within the price range he/she has specified.
Usability : The user interface should be so designed that the customer with least awareness should also be able to use it. At every step, beginning from login, book search, adding to cart till processing the payment, there should be guidelines helping the user to perform the activity.
Maintainability: This can be included by making sure that the system is available 99.99% of the time in a year. This means the system can down for in whole for 52 minutes in a year.

Online book store

USer

Book search

Customer Login

Class Dia

Class Dia

Lab Evaluation 2 – Anudeep

class sequence usecae

 

Software Process Model

Spiral Model, since requirement keep on changing.

Design principle

Object oriented Programming.

Universal Design
1. Very Simple to use and update more information
2. Interface is well visible to user

Lab evaluation 2 – Vanayak R.H

act cls seq usc

Lab Evaluation 2 – Sunny

use case digram sequence class diagram

 

Software Process Model

Implemented model is Spiral Model, since requirement keep on changing. There is a need of adding new books in database as well as new customer are also registered.

Design principle

This can be developed using Object oriented Programming.

Universal Design have been also considered
1. Very Simple to use and update more information
2. Interface is well visible to user
3.Redo And Undo option is also provided. user can select and deselect option.

LAB Evaluation2..- Manjunatha M

class usecase sequence activity

Agile Software Development Methodologies

The term Agile itself means “quickness”. When applied to software engineering, it refers to quicker delivery of software to the customer with greater satisfaction and stronger hold in the competitive market. The Agile movement started almost 11 years back. It can be said that Agile has its roots from 1992 with Crystal being the starting point [1].
The main intention of agile is to develop the software in iterations (called sprint) so that they have a visible outcome after every iteration. After each iteration the current working software is shown to customer to ensure that their requirements are correctly captured and understood. The development begins by including the higher priority requirements in the 1st iteration and subsequently adding more complexity to it. At the end, the concern is that customer should be satisfied with the software and not whether the original stated requirements are met. The agile teams should comprise of people who are technically strong and must be volunteer. This is because more value can be added in the development only by an interested team member rather than a member involved forcefully.

Along with these benefits agile methodologies have certain limitations:

1) If a team is spread across different geographical location then it is difficult for them to interact daily. This also applies to interacting with customer. The team and the customer must be co-located for better interactions.
2) Agile believes in least documentation [2]. Suppose a software developed using agile methodology needs to be enhanced and a new development team will be taking up this task (earlier developers may not be available). Then in such a situation it would be very difficult and time consuming for new developers to understand the software, as there will be no document explaining internal operation details.

References:

[1] Udayan Banerjee, http://setandbma.wordpress.com/2012/03/23/agile-history/ , Gives the brief history of agile movement i.e., from when did the movement start and details about the 17 contributors of this movement.
[2] Jim Highsmith, Alistair Cockburn: “Agile Software Development: The Business of Innovation”

lab evaluation – Anudeep

anuanu1

lab evaluation 1 – sunny

gantt chart resources usages resources

lab evaluation – Bilal

Screenshot from 2013-01-19 11_23_26 Screenshot from 2013-01-19 11_21_24Screenshot from 2013-01-19 11_22_31

Lab Evaluation 1

Lab Evaluation 1

task-list1.png

Lab-evaluation 1

Lab-evaluation 1

Task-1: Initiation : define objectives for the project,
task-2: planning: gathers requirement, cost estimation, production document, assigned to project manager, sqa
task-3: designing: design layout for seven modules–> a home page for product catalog
–> Search
–> advance search
–> Book description : ASSIGNED TO DESIGNER
–>User voting
–> Shopping cart
–> managing user accounts
task-4: coding: coding for seven modules-> a home page for product catalog
–> Search
–> advance search
–> Book description : assigned to developer
–>User voting
–> Shopping cart
–> managing user accounts
task-5: Testing: test the software: assigned to tester

BY SMITA TANK

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: