Thursday, December 11, 2014

Free mca project synopsis

Free mca project synopsis

When a user interacts with a web application, the interaction occurs through one or more mechanisms which are called interface mechanisms. Testing done within theses mechanisms is the interface mechanism testing. This testing is done in following areas.
Free mca project synopsis Links:
Each navigation link is tested to ensure that appropriate web page is linked or not. I have listed all the links in each form to test whether each link is connecting the appropriate page or not.
Testing forms has been done at two different levels i.e. at minimum level and at more targeted level. At minimum level I have tested for:
  • Whether labels been correctly defined for fields or not.
  • Whether server is receiving all the information contained in the form and no data are lost in the transmission between client and server.
  • Whether appropriate default values are available when the user does not select any item in the selection box.
  • Whether scripts that perform data validation from the client-side are working properly or not.
At more targeted level I have tested for:
  • Whether text fields have proper width to enter data.
  • Whether text fields are allowing string length more than specified length.
  • Whether tab order among different controls is in required order or not.
Client Side Scripting:
Each and every function written in scripting has been tested by Black Box Testing.
I have combined the forms testing with this client-side script testing, because input for scripting is provided from forms. Some methods of scripting will be performed in some particular browsers and in others not. So I have also performed compatibility testing to ensure that the scripting functions will work properly in all browsers.

 MCA project synopsis - USABILITY TESTS

In this testing I have verified up to, which level that, users can interact with the system effectively. Tests are designed to determine the degree to which the web application interface makes users easy to work with. I have designed test case so that usability testing can be verified at different levels:
  • Usability test has been performed on each and every individual interface i.e. forms.
  • Usability test has been performed on total web page with related client side scripting functions.
  • Usability test has been performed on total web application.


As this is a web application, it should run on different environments like different computer architectures, operating systems, browsers and network connection speeds.
As different computing configurations can result in difference in client side scripting speeds and display resolution, operating system variance may cause web application processing issues.

Different browsers produce slightly different result as we expected, in some cases this results may not be a problem but in some cases there will be serious errors.

To perform these testing strategies first we have prepared what are all the client side functions that encounter problems with different compatibilities. In essence of those we have tested by identifying different computing platform, typical display devices, the operating systems supported on the platform, the browsers that are available with me.

NAVIGATION TESTING of mca .net project 

Navigability is tested to ensure that all navigation syntax and semantics are exercised to uncover any navigation errors. (ex: dead links, improper links, erroneous links). The job of navigation testing is to ensure that the navigation mechanisms are functional, and to validate that each Navigation Semantic Unit can be achieved by the appropriate user category.
We have done the navigation testing in following areas.
·         Navigation links are thoroughly tested.
·         Redirects are properly checked.
·         Is the target page to a navigation link is correct or not.
·         Is the link caption meaningful or not.

8. DEPLOYMENT of  mca .net project 


The error-free project, which passed all the tests, is now deployed at the client environment in this phase.

free mca project reports

Free MCA Project Reports

BCA MCA Bsc B tech CS information technology final year project

Testing is the process of exercising software with the intent of finding errors. The Web-app testing is a collection of related activities with a single goal: to uncover errors in web application content, function, usability, navigability, performance, capacity and security.
There are several areas of testing involved in web applications. For the current web application, I used some of them as follows.
Mca Project Content testing attempts to uncover errors in content of the web application. In addition to examining static content for errors, this testing step also considers dynamic content derived from data maintained as a part of database system that has been integrated with the web application.
Content testing of all web pages is evaluated for syntactic and semantic errors.
At syntactic level I have verified the content for spelling, punctuation and any grammar mistakes of all pages which contain the content of the website.
At semantic level I have verified for the following aspects.
o   Whether the content is valid or not.
o   Whether the format of the content is good and readable or not.
o   Whether all the web pages are showing consistent content or not.
The content includes the dynamic information about the companies, stock values and flowchart details which is fetched from the database. The consistency of this information is thoroughly tested.
Database testing is done to uncover the errors which occur as a consequence of fetching large equities of data from the database, extracting relevant data from the database, accessing the database using several queries etc,
In this project, I have tested the application for database errors in following areas.
o   While converting the user request into a database query
o   While fetching dynamic content to the web pages.
o   While opening and closing the active connections to the database
o   While presenting the raw data fetched from database in a formatted HTML output.
o   Communication between the web application and the remote database.
          All the interfaces that have been designed are reviewed whether they meet the customer requirement or not. While testing all interfaces I have verified for errors as follows.

  • Errors related to specific interface mechanisms for example proper execution of all menu links that are provided in each web page
  • Errors related to all semantics of navigation and web application functionally that is provided in each web page.
  • Errors in consistency related to different aspects of the interfaces like font style, color, size, screen background color etc.,
  • Errors in viewing the interfaces in different web browsers like Microsoft internet explorer, Mozilla firefox etc.,

Free MCA Projects with Documentation

Free MCA Projects with Documentation

MCA Project Test Case Design:
In this step, we design all the test cases, which are used by the testers to test the application after construction. Test case is nothing but a sample input or sample activity performed to test for any errors or bugs in the application. In order to perform system testing, we’ve developed many test cases. Some of them are as follows.

Expected Behavior
Observed Behavior
Enter the Wrong login-id and password to login
Error Message indicating the status of the user
Enter correct hint answer in password recovery form to recover password
Display the password of the user
Enter an existing login-id in the user registration form
Error message “login_id already exists. Please choose another one”.
Delete a gallery which contains products
Error message “Gallery cannot deleted because it is not empty.”
Enter bid amount less than base price
Error message “Bid cannot be evaluated as the bid price is less than base price.”
Send message without body
It should display an error message “Message body cannot be blank”


This is the actual constructive phase of the project where the models and designs are added with functionality. The construction phase involves coding, compiling and building the functional modules of the project.

Free MCA Projects with source code

Free MCA Projects with source code

In this phase, we provide a physical shape to all the models that are created in the analysis phase. The design phase is used to physically create different elements of the project. This phase involves the following sub-phases.
5.1.   MCA Project Module Design:

BCA MCA Bsc B tech CS information technology final year project

In this step, we identify the modules and sub-modules of the project. Module is the functional unit of a project. The modularity of a project depends upon the functional requirements and also the users of the project.  In this step, we identify the modules and sub-modules of the project. Module is the functional unit of a project. The modularity of a project depends upon the functional requirements and also the users of the project.
In this project, following functional modules are identified.
Ø  Administrator: This module involves all the functionalities meant for the administrator.
Ø  Agent: This module involves all the functionalities meant for the agent.
Ø  CUSTOMER: This module involves all the functionalities meant for the customer

5.2.   MCA Project Data Design:
Data dictionary is a document, which describes the database design of the project. In this step, we generate the data dictionary using the E-R Model of the system. Each entity is represented as a table here. The Data dictionary describes the tables, their fields, data types and constraints on the fields. The Data Design transforms the information domain model created during analysis into the data structure that will be required to implement the software.
MCA Project Data Design is the first of three design activities that are conducted during software engineering. The impact of data structure on program structures and procedural complexity cases data design to have a profound influence on software quality. The concept of information hiding and data abstraction provides the foundation for an approach to data design. The primary activity during data design is to select logical representation of data objects (data dictionary) identified during the requirements definitions and specifications phase.
It is the process of designing database files, which are the key source of information to the system. The files should properly, designed planed for collection, accumulation, editing the required information. The objectives of the file design are to provide affective auxiliary storage and to contribute to the overall efficiency of the computer program components to the system.
        A relation R of this system is said to be in first normal form, if all domains contain atomic values.
In this project the Data in each table has atomic values but the data are redundant. so, I consider next normal form i.e., Second normal form.
        A relation R of this system is in second normal form as if every irreducibly dependent on primary key. Coming to child tables we will be having a reference to the primary key of master table.
In this project I normalized the data tables up to second normal form.

5.3.   MCA PROJECT Interface Design:

In this step, we design all the interfaces for the application. Interface is the medium between the user and the system. We consider all the client specifications while designing the screens and reports.
Every user interface has been designed so that the system provides all the characteristics like easy to use, less number of keystrokes to complete an action, less usage of left hand, easy too learn, easy to navigate, consistent, error-free and functional.
The entire interface that has designed with the features listed below:
·          Every action is provided with a prompting message. So that it provides a better communication.
·         Every interface maintained consistent navigation, menus, icons, colors, shape and layout.

Every page has been designed so that it optimizes the user’s work efficiency.

free download use case Diagram of java projects with source code and description

 java projects Use case Diagrams

BCA MCA Bsc B tech CS information technology final year project

1.    Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is on what a system does rather than how.
2.    Use case diagrams are closely connected to scenarios. A scenario is an example of what happens when someone interacts with the system.
3.    A use case is a summary of scenarios for a single task or goal. An actor is who or what initiates the events involved in that task. Actors are simply roles that people or objects play.
4.    A use case diagram is a collection of actors, use cases, and their communications.
Use case diagrams are helpful in three areas:
Ø  Determining features (requirements). New use cases often generate new requirements as the system is analyzed and the design takes shape.
Ø  Communicating with clients. Their notational simplicity makes use case diagrams a good way for developers to communicate with clients.
Ø  Generating test cases. The collection of scenarios for a use case may suggest a suite of test cases for those scenarios.

 java projects Class Diagrams

1.    A Class diagram gives an overview of a system by showing its classes and the relationships among them.
2.    Class diagrams are static. They display what interacts but not what happens when they do interact.
Ø  UML class notation is a rectangle divided into three parts: class name, attributes, and operations.
Ø  Names of abstract classes are in italics. [example: Payment]
Ø  Relationships between classes are the connecting links.

1.    Association -- a relationship between instances of the two classes. There is an association between two classes if an instance of one class must know about the other in order to perform its work. In a diagram, an association is a link connecting two classes.
2.    Aggregation -- an association in which one class belongs to a collection. An aggregation has a diamond end pointing to the part containing the whole. In our diagram, Order has a collection of OrderDetails.
3.    Generalization -- an inheritance link indicating one class is a superclass of the other. A generalization has a triangle pointing to the super class. Payment is a super class of Cash, Check, and Credit.
4.    Composition -- Each instance of type Circle seems to contain an instance of type Point. Composition relationships are a strong form of containment or aggregation. Aggregation is a whole/part relationship. Composition also indicates that the lifetime of Point is dependent upon Circle. This means that if Circle is destroyed, Point will be destroyed with it.
Ø  An association has two ends. An end may have a role name to clarify the nature of the association. For example, an OrderDetail is a line item of each Order.
Ø  A navigability arrow on an association shows which direction the association can be traversed or queried. An OrderDetail can be queried about its Item, but not the other way around. The arrow also lets you know who "owns" the association's implementation; in this case, OrderDetail has an Item. Associations with no navigability arrows are bi-directional.
Ø  The multiplicity of an association end is the number of possible instances of the class associated with a single instance of the other end. Multiplicities are single numbers or ranges of numbers. In our example, there can be only one Customer for each Order, but a Customer can have any number of Orders.
Ø  Every class diagram has classes, associations, and multiplicities. Navigability and roles are optional items placed in a diagram to provide clarity.
Ø  Packages appear as rectangles with small tabs at the top. The package name is on the tab or inside the rectangle.
Ø  The dotted arrows are dependencies. One package depends on another if changes in the other could possibly force changes in the first.

Object Diagrams

1.    Object diagrams show instances instead of classes.
2.    They are useful for explaining small pieces with complicated relationships, especially recursive relationships.
Ø  Each rectangle in the object diagram corresponds to a single instance. Instance names are underlined in UML diagrams. Class or instance names may be omitted from object diagrams as long as the diagram meaning is still clear.

Sequence Diagrams

1.    Class and object diagrams are static model views. Interaction diagrams are dynamic. They describe how objects collaborate.
2.    A sequence diagram is an interaction diagram that details how operations are carried out -- what messages are sent and when.
3.    Sequence diagrams are organized according to time. The time progresses as you go down the page.
4.    The objects involved in the operation are listed from left to right according to when they take part in the message sequence.

Collaboration Diagrams

1.    Collaboration diagrams are also interaction diagrams.
2.    They convey the same information as sequence diagrams, but they focus on object roles instead of the times that messages are sent.
3.    In a sequence diagram, object roles are the vertices and messages are the connecting links.

Ø  The object-role rectangles are labeled with either class or object names (or both). Class names are preceded by colons ( : ).
Ø  Each message in a collaboration diagram has a sequence number. The top-level message is numbered 1. Messages at the same level (sent during the same call) have the same decimal prefix but suffixes of 1, 2, etc. according to when they occur.

Statechart Diagrams

1.    Objects have behaviors and state. The state of an object depends on its current activity or condition.
2.    A statechart diagram shows the possible states of the object and the transitions that cause a change in state.
Ø  This diagram has two self-transition, one on Getting SSN and another on Getting PIN.
Ø  While in its Validating state, the object does not wait for an outside event to trigger a transition. Instead, it performs an activity. The result of that activity determines its subsequent state.
Ø  States are rounded rectangles.
Ø  Transitions are arrows from one state to another. Events or conditions that trigger transitions are written beside the arrows.
Ø  The initial state (black circle) is a dummy to start the action. Final states are also dummy states that terminate the action.
Ø  The action that occurs as a result of an event or condition is expressed in the form /action.

Activity Diagrams

1.    An activity diagram is essentially a fancy flowchart. Activity diagrams and statechart diagrams are related.
2.    While a statechart diagram focuses attention on an object undergoing a process (or on a process as an object), an activity diagram focuses on the flow of activities involved in a single process.
3.    The activity diagram shows the how those activities depend on one another.
Ø  The process begins at the black start circle at the top and ends at the concentric white/black stop circles at the bottom. The activities are rounded rectangles.
Ø  Activity diagrams can be divided into object swimlanes that determine which object is responsible for which activity. A single transition comes out of each activity, connecting it to the next activity.
Ø  A transition may branch into two or more mutually exclusive transitions. Guard expressions (inside [ ]) label the transitions coming out of a branch. A branch and its subsequent merge marking the end of the branch appear in the diagram as hollow diamonds.
Ø  A transition may fork into two or more parallel activities. The fork an
Ø   The subsequent join of the threads coming out of the fork appear in the diagram as solid bars.

Component & Deployment Diagrams

1.    A component is a code module. Component diagrams are physical analogs of class diagram. Deployment diagrams show the physical configurations of software and hardware.
Ø  The physical hardware is made up of nodes. Each component belongs on a node. Components are shown as rectangles with two tabs at the upper left.

            A system is simply a set of components that interact to accomplish some purpose.
      Systems are of two types.
·          Open Systems.
·         Closed Systems.

          Systems that interact with their environments are open systems. They receive input   and produce output. In contrast; systems that do not interact with their surroundings are
closed systems all ongoing systems are open. Closed systems exist only as a concept.

        System development can generally be thought of as having two major components
·         System Analysis.
·         System Design.

          System analysis is the process of gathering and interpreting facts, diagnosing problems, and using the information to recommend improvements to the system. System Design is the process of planning a new business system or one to replace or complement an existing system.

          Systems analysis is about understanding situations, not solving problems. Effective analysts therefore emphasize investigation and questioning to learn how the system currently operates and to identify the requirements users have for a new or modified one. Only after analysts fully understand the system are they able to analyze it and assemble recommendations for system design.

           The manner in which a systems investigation is conducted will determine whether the appropriate information is gathered. In turn, having the right information influences the quality of the application that follows .in other words, good system design, whether developed through the SDLC method, prototyping, or structured methods, begins by documenting the current system and proper diagnosing the systems requirements.