Visual Basic

26-Jan-09 22:44

Hi, I'm new to VB.Net.
I want help to develop a Time sheet project.

Abstract:
employees log-in and log-out time has to be entered,hours worked on a particular project has to be entered,status of the projects should be managed,personnel information of the employee has to be maintained,payroll report has to be prepared with the information.

Can anyone guide me on this.

Thanks in Advance

Eddy Vluggen26-Jan-09 23:55

Eddy Vluggen

26-Jan-09 23:55

Take a look at the "Employee Starter Kit" and the "Time Tracker Starter Kit" Smile | :)

Your question is rather broad. You'll need to create a database and a GUI - but most off all, you'll need to define some specifications. Where are the employees names' stored? Are you going to retrieve them from an Active Directory? Or do they sign-in in your application? What information is expected in the payroll report? Do they have to include special rates for working in the weekends?

Lots of questions, hope they help to get you started.

I are troll Smile | :)

vijay248227-Jan-09 1:26

Timesheet project in VB.NET Abstract

27-Jan-09 1:26

thanks for ur reply.
it would definitely help me to prepare a detailed specification.
will soon get to u with the spec

thanks a lot Smile | :)

vijay248228-Jan-09 1:20

28-Jan-09 1:20

Aim:
A web based system which manages the Project related activities as well as Team related activities at a central location.

Abstract:
This system captures all the daily activities of the project and team and provides the appropriate interface to manage both the type of data in a centralized location.
The system works on level wise. This means that: Department manager, Project Manger, Project Leader and Team member have different types of login accounts.
The system provides a graphical representation of individual utilizations.
It generates weekly or monthly timesheet reports.
Relevant information regarding projects and teams are always available to the users which makes them well informed about the status.

Level wise system activity: Team Members

They input daily timesheet and leave details into the system.
System provides them with the summary of their inputs.
System also provides them with the progress of the project.
It provides them with their utilizations.

Level wise system activity: Project Leaders/Project managers

Adding new packages to the projects.
Allocating team members to the packages.
The system provides the Team Performance, Package progress, generates individual time sheets for team members.

Kindly help me out with this abstract/specification

Thanks

Eddy Vluggen28-Jan-09 2:53

Eddy Vluggen

28-Jan-09 2:53

That's a good start actually Smile | :)

You've now got a short list of what the customer expects of the application. Lets call this the "Customer Spec". The track described here is loosely based on a formal approach. That means that it's more time-consuming than just firing up Visual Studio and starting to pound code - whether that's worth your time, is up to you.

The extra documentation gives a better view on the size of the project, and thus gives you a better indication of the time required to build it. It's a lot of work, and some steps may seem trivial enough to skip. To sum it, there are three important documents that are generally 'done';

- A definition study
Being a short list of wishes on which you base the Functional Specs. We named this the "Customer Spec", and you've already completed it.

- A functional specification
Detailing how each screen will look, what the different buttons do and so forth. This is based on the previous document, and will give your customer an idea what to expect.

- A technical specification
Detailing how you're going to build the screens that you mentioned in the funtional specification.

Following this route, you'd need to build a Functional Spec next. Joel Spolsky has done some great articles on the writing of functional specifications that you can find here;

Painless Functional Specifications
* Part 1: Why Bother?
* Part 2: What's a spec?
* Part 3: But.. How?
* Part 4: Tips

There are two examples on his site that you can view;
* WhatTimeIsIt (An example specs based on a fictional product)
* The Aardvark Spec (Real spec from a real product)

Once that is done, you could opt to translate this functional design (how does it look & work) to a technical design (how is it going to work?)

vijay2482 wrote:
Aim:
A web based system which manages the Project related activities as well as Team related activities at a central location.

Here you have identified two important entities. You'll have to flesh them out into detail in the TechSpecs; what facts are you going to store about a project? What facts are you going to store of a Team? How do the entities relate to each other?

This is the start of your database-design, and might look something like this for Project:

Table: Project
----------------------------------------------
ProjectNumber (number)
ProjectName (text)
ProjectInitiationDate (datetime)
ProjectDescription (text)
ProjectLeader (reference to Employee-table, or just text?)

Defining these things helps in creating the structure. As it shows in the example above, it's not sure from the "Customer Spec" whether it's enough to store the name of the project-leader. These kind of "holes" in the design become apparent once you start working out the structure.

vijay2482 wrote:
The system works on level wise. This means that: Department manager, Project Manger, Project Leader and Team member have different types of login accounts.
The system provides a graphical representation of individual utilizations.

Let's call the different types of login accounts "Roles". A "Employee" has a "Role", and depending on his/her Role, they can or cannot view/do things. ASP.NET has some standard-controls that could help you provide this functionality. More information on Users and Roles can be found here[^].

vijay2482 wrote:
It generates weekly or monthly timesheet reports.
Relevant information regarding projects and teams are always available to the users which makes them well informed about the status.

Do you have examples of how these should look like? What information does the weekly report contain? What SQL-queries would you need to retrieve that information from your previously defined model?

That's a lot of questions to answer, and like I said before, it's a lot of work. Then again, it's easier to change the specs then it is to change sourcecode Smile | :)

Hope this helps,

I are troll Smile | :)

vijay248228-Jan-09 5:48

28-Jan-09 5:48

oh, their is a lot to do in documentation before starting the coding
will start to do each spec and understand the essentials before getting into the scripting work

thanks

Eddy Vluggen29-Jan-09 2:12

Eddy Vluggen

29-Jan-09 2:12

vijay2482 wrote:
oh, their is a lot to do in documentation before starting the coding

Documentation is the first thing that's skipped.. Still, I wouldn't want to build a house without a plan and some drawings.

Documentation is also a way to protect yourself. Your customer/boss/employer might think that it's easy to write a 'small' TimeSheet-project, and he might start making a list of features/reports/wishes that's long enough to keep 10 programmers occupied for a year. The document breaks your assignment into pieces, and lot's of pieces are lots of work.

I just hope that I didn't discourage you with the amount of documentation Big Grin | :-D

I are troll Smile | :)

gsuryaprasath13-Jul-11 18:42

gsuryaprasath

13-Jul-11 18:42

Abstract Classes

An abstract class is the one that is not used to create objects. An abstract class is designed to act as a base class (to be inherited by other classes). Abstract class is a design concept in program development and provides a base upon which other classes are built. Abstract classes are similar to interfaces. After declaring an abstract class, it cannot be instantiated on it's own, it must be inherited. Like interfaces, abstract classes can specify members that must be implemented in inheriting classes. Unlike interfaces, a class can inherit only one abstract class. Abstract classes can only specify members that should be implemented by all inheriting classes.

More Details : Abstract

Ashutosh Phoujdar27-Jan-09 19:53

Ashutosh Phoujdar

27-Jan-09 19:53

I would like to suggest for trying to download Time Tracker Starter Kit[^] Smile | :)

dnpro
"Very bad programmer"

My Latest Articles
RichTextBox Control with Find functionality
LogViewer - A Simple Log Listening Utility

vijay248227-Jan-09 20:23