1 .

1 Introduction to Organization
1.1.1 Do you know who we are?
When you think data, you think basic. When you deal with data, you deal with the
essence.And when you have data, you have the core.

Here comes IDEALJOB role in dealing with all kinds of data and information utilizing
the latest tools and up-to-date strategies to benefit from this powerful asset any company
has (DATA).

1.1.2 But what kind of data components do we really handle?

To answer this question, here is a set of examples like Image & Document Management,
Business Process, E-forms, Web Services Collaboration, Portals, Search Engines, Media
Management, Resource Management, Networking, Business Continuity and Messaging
& E-mail Management.
As a result, our customers will enjoy secure sources for instant access to business-critical
information from unified presentation layer through portals accessing information and
business application online without worrying about where or when.
What’s more assuring to deal with Dream Recruitment is to know that we have global
partners whose know-how experiences are pioneering in their fields. To mention few
names, we have GXS, EMC Documented, Oracle, Microsoft, MIRO, HP, and Sikh. We
all together combine a powerful practice of information management to reach our
objectives of providing our users the best data solutions, bar none.

1.1.3 We have a GOAL. We have a MISSION.

We are here for a reason. Of course, we didn’t build our name for nothing. Going through
the years and moving from one achievement to another and one success to a bigger one
never make us forget why we’re here for. For us, our mission isn’t actually a mission but
a pride we hold in our business.
From hardware and software to infrastructure and services, Dream Recruitment dedicates
its efforts to creative tailor-made solutions for users and employs data to help improve
user’s business performance in all possible means.

1.1.4 We can see it

Dealing with data is our main specialty. We access, analyze, store, share, manage, collect,
protect, and deliver data using nothing but the best quality available in the market.

1.1.5. Here’s a list of what we do

 Business Process Management Solution
 Business Enterprise Portal Solutions
 Enterprise Resources Planning
 Facilities Asset Management System (FAMS)
  Healthcare Information Services
 IT Infrastructure
 Datacenter Solutions
 Storage Solutions
 Virtualization and Consolidation
 Information Security
 Disaster Recovery
 Website Design and Development
 B2C E-Commerce
 Bahrain Flights & Weather Service
 Component Development
 eRecruitment

1.1.6. The Current Methods

While existing systems for controlling PvP show some very creative design solutions,
each of the following strategies nonetheless suffers from certain flaws that arise from
the different priorities assigned to play game elements.
Administrative Control (Simutronics’ Gemstone and Dragonrealms) Simutronics
gives its players wide leeway in resolving conflicts among themselves, and generally
limits its hard-coded restrictions on attacking other characters. New players may not
be attacked and are not strong enough to harm one another. Stealing from a person’s
Online Recruitment System is limited to coins and small gems, and corpse looting is
either not possible (as in Gemstone III) or has safeguards that allow careful players to
prevent it from happening (as is the case in Dragonrealms). The leeway afforded the
players allows the responsible players a great degree of freedom in how they play
their characters. To balance out this freedom, though, Simutronics strictly polices its
player base. Its players’ terms and conditions agreement, for example, states, “What is
not acceptable is to initiate combat against unsuspecting victims. Anyone exhibiting
such behavior, especially one who chooses to prey upon weaker players for his or her
own enjoyment, may be in violation of…policy.”

1.2. BUSINESS RULES CATALOG

1.2.1 Introduction
Business Rules catalog means all the requirements are considered in this section as a
whole.

1.2.2. Description
Detailed description of the rule. Typically written in structured English or pseudo code.
Consider using a flowchart or UML activity diagram to depict procedural logic.

1.2.3. Example:
Sometimes a business rule is easier to understand when one or more examples are
provided.
1.2.4. Related Rules:
List other business rules related to this one. Word Tip: If you mark each business rule
with a heading type (e.g. Heading 1, Heading 2,) you can then add an automatic link to
the rule by inserting a cross-reference (Insert menu, Cross-reference item, and then insert
a heading.

1.2.5. Reference(s):
Applicable references, such as explanatory documents (printed or electronic), pertinent to
this business rule.

1.2.6. Notes:
Optional section.
List an "to dos", concerns to be addressed, …
List any important decisions made during the development of this business rule.

1.3. PROBLEM DEFINITION

Problem definition is the activity of translating the information gathered during the
analysis activity into a document that defines a set of problems. These should accurately
reflect what the Patient wants. This document must be written so that it can be understood
by the end user and the system Patient.
Problem definition is concerned with the functionality that must be delivered. We visited
the Punjab Diagnostic Centre. Currently Idealjobs Managements managing their
operations manually. Idealjobs management has decided to completely automate the
whole business processes of the company. Also in order to increase their sales, Idealjobs
management wants to have fully automated system.

1.3.1. Manual System: It is a manual system, which is handled by some clerks. The
Clerk has to enter all the data entries. In case of damage to any of these registers would
result in losing the data entered.
1.3.2. Duplicate Data Entry: As it is said,” to err is human.” therefore the clerk may
make mistake by entering the same data again, which may produce redundancy.

1.3.3. Searching Problem: There is also a problem for searching the data. For example
if the data record for the Patient or Sale Order is to be retrieved then there is no quick
way of searching this record.
1.3.4. Loss of Time: It is usually said that time is money. The primary concern in many
things is the time factor. There is much more time consumption as all the data entry and
retrieval is done manually.

1.3.5. Maintenance difficulty: It is not easy to maintain the data properly. It is difficult
to maintain Patients, vendor’s record.

1.4. REQUIREMENTS ENGINEERING

1.4.1. Requirements:
Problem descriptions and Solution specifications.

1.4.2. Engineering:
Cycle of problem analysis, solution, specification and analysis, solution
Implementation and implementation analysis.

1.4.3. Stages in requirements engineering:

 Elicitation
 Conceptual Modeling and Analysis
 Validation

1.4.4. Communication and negotiation:

 Specs as outcome.
 After this
 IDEALJOBS technical design and development.

1.4.5. Software Specifications:

These are the basic objects that relate to project through which we undergo development
of our project are as follow.

1.4.6. Requirement Specification.

To understand the nature of the program(s) to be built, the software engineer or analyst
must understand the information domain for the software as well as required function,
behavior, performance and interfacing. Requirements for both the system and the
software are documented and reviewed with the customer. Deals with System constraints
on input and output (Functional and non functional requirements). We have raw data to
deal with requirements input and outputs considering all constraints.
1.4.7. Functional Requirements
It requires number of meeting with clients and meeting of staff that the human resource
department arranges every Week at Saturday for the improvement of work in the
organization.
And interaction of departments and the data flow of these departments and some other
kind of requirements are obtained. Means that meet through the technology which we
have adopted. The basic theme is what is output suite required by the user through
randomly generated by the function specification considering all constraint and future
needs.

1.5. STANDARDS.
Standardization of the system, provide company head with document to review at
developmental to determine the requirements to extend;
 Record technical information in (development and modification)
 Provide authors of documents to head of project a development Guide.
 Provide consistency of format.

1.5.1. Quality Standard

This is an issue deals with every software development organization to work with
programming standards that decrease the development errors greatly improve software
quality.

1.5.2. Maintainability Standard:

Software Systems, Standards to identify the name of modules and classes to achieve the
understanding and easy to trace and debug.
This, in turn, reduces the time when upgrading the software and also for its
Maintenance.

1.5.3. Database Standard.

Database deals with the sets of the shared data through query. It is necessary to develop
data resource. We need to understand the technical background of computer management
for the data. Database standards include standard field lengths, naming conventions for
field.

1.5.4. GUI Standard:

It is the interface used by user to work with application. The controls and text view is to
be up to standard which make user to easily set with application. Controls of system
should be using mouse and keyboard at least. Convention should be followed in coloring
1.5.5. Coding Standard:
We should use indentation for coding or program or software that can be more readable
and easy to understand. It also helps us to maintain and debug the software.

1.5.6. Programming Standard:

It should be on standard with predefined set of rules for algorithms. In programming we
have to consider access time, reliability and extendibility.

1.6. PERSPECTIVES ON SOFTWARE ENGINEERING:

1.6.1. Quality of Software
The average software product released on the market is not error free
 Irregular Shutdowns
 Misbehavior (MS Excel)
 Updates are needed to meet users requirements
 Bug, Problems, Failures
 Misunderstanding requirements leads to functional misbehavior
 Errors in code
 Standard software: 25 bugs per 1.000 lines of program
 Windows95: 200.000 errors (!) in 10 Millions lines
 Exploding costs during development
 Delivery Date cannot be met
 Organizational structure changes
 Software Engineering is a collection of techniques, methodologies and tools
that help with the production of a high quality software system with a given budget
 While change occurs.
 Computer Scientist
 Proves theorems about algorithms, designs languages, defines
 knowledge representation schemes
 Has infinite time…
 Engineer
 Develops a solution for an application-specific problem for a client
 Uses computers & languages, tools, techniques, and methods
 Software Engineer
 Works in multiple application domains
 Has only 3 months...
 While changes occurs in requirements and available technology
1.7. Actors Catalogue
1.7.1. Administrator

1.7.2. Jobseeker

1.7.3. Employer

1.7.4. Visitors/guests
1.8. Use Cases.

1.8.1 Admin Use Cases.

1.8.2 Job seeker login.
1.8.3 Employer login.
1.8.4 User/guest.
1.9. Draft List of Requirement
1.9.1. Functional Requirements
In functional specification declare all functions and needs of software as that
given below.
1.9.2. Business Requirements
The organization was to want produce like that students that fulfill all our country
requirements and they have enough knowledge of circuit making Web
development, laws and functions.
They must have theoretical as well as practical knowledge of hardware
And it is possible only when they have such any system.
1.9.3. User Requirements:
All users it mean teacher and students need a proper channel for best
understanding internally working of Website.
Such as teacher wants to deliver his lecture in such way his students can easily
understand his lecture and give a good response.
And students want to understand everything about Website making, and want to
see graphically working anything about it that make them able.
They raise the image of their institute.
1.9.4. Operation Requirements:
For operational requirements it is necessary for software engineer that he take a
good view about that what the necessities are for make such software that fulfill
the needs the needs of user requirements.
For this purpose I when I take a deep view of user requirements so decide I will
make a system that show graphically internal working of Web development or
functions that are using in inside the Website.
So I select Visual Basic .Net because I find it suitable for my software
requirements, and I start working on it
1.9.4.1. CONCEPTUAL DESIGN:
DESIGN:
I divided this phase into two steps:
 Logical Design
 Physical Design
1.9.4.2. LOGICAL DESIGN:
In this part of third phase I made the specifications about the design of the UML
design.
The considerations Ire:
 Number of pages
 Layouts
 Sketches allocation of data to relevant pages.
By considering all the options I made layouts on the paper. This stage was totally
on hard paper. After having made all the layouts I get it checked from the client
and by having a compliment from their side I proceeded to next part of the design
phase.

1.9.4.3. PHYSICAL DESIGN:

In this stage I converted all the logical design that was on the paper to computer
and made a soft copy of it.
After matching the specific pages. I have defined their relevant features, wording
and pictures that made it more attractive.
By having it approved from my client I started for the development phase.

1.10. Non-Functional Requirements

Non-function requirements those which are not specify by the end-user but these
are implemented to fulfil the functional requirements.

1.10.1. Step 1: Selecting a treatment

Firstly, select the medication of your choice from the treatment options available,
and then indicate the dosage you would like to order. If you are unsure about
which dosage you should choose, we recommend you start off with the lowest one
available. If it does not provide you with the results you are looking for, you can
select a higher dose the next time you order.
1.10.2. Step 2: Patient registration
After you have selected your treatment, you will be prompted to log-in to your
account. If you don’t have an account already, you can create one quickly and
easily. You will be able to pass over this step if you have already logged-in.
1.10.3. Step 3: Medical consultation
The medical consultation is the most important step. You will need to provide
answers to a few short medical questions about your condition. These details are
vital, as they will enable our doctor to diagnose your condition and evaluate
whether your selected treatment is suitable for you to use. Try and provide
answers in as much detail as possible, as this will help our doctors to get all the
information they need to approve your consultation.
1.10.4. Step 4: Delivery and billing address details
After completing your consultation form, you will be asked to provide your
billing and delivery address details. Your billing address is the address where your
credit or debit card is registered to. To ensure that your order does not get delayed,
always double check that this address is entered correctly. We can deliver to your
home, office, hotel or any other valid address that is convenient for you to receive
your medication.
1.10.5. Step 5: Your payment details
The last step of the ordering process is your billing details. There are a wide
variety of payment options available; you can make payments via Online Cash,
via your local Pay Point store with cash or card, by cheque, postal order. We will
not take any money from your account at this stage; we only take payment when
your order is approved by our doctor.