Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Information management application

Status
Not open for further replies.

buxtonicer1

Programmer
Sep 20, 2006
82
GB
I’ve been given a project at work which is essentially needed to capture the various environments (IT) data within the organisation. By environments I’m talking about hardware, databases, application servers, web servers, database hostnames, usage, storage, application owner and so on. It is effectively an Environments Management Inventory System.
For the initial pitch I’ve been given two weeks to put together an application that will give the client an idea of what is achievable going forward. The data required for the project is being collected by someone else. I have been tasked with producing a simple web application that is interactive and easier to read and navigate than the traditional and much hated spreadsheet. I’ve written .net applications before so that is not the issue. I’m just curious as to what will be the best way of designing something in two weeks. I mean the information will be stored in some tables in a database. But is there any thing out there that I should look into. I mean pulling the data back to a data grid seems the same old thing and not that much better than an online Microsoft spreadsheet.
Why I’m posting on the site is well you guys are experienced c# developers with many years experience. I’m sure someone has been tasked with something similar in the past. I would be interested in getting your opinion on the above task.
 
Two weeks? That's a big ask.

Congfiguration management systems are usually based around the concept of a configuration item (CI). You can have different types (subclasses, I guess) of CI, and CIs can contain other CIs (GoF Composite pattern).

So, for example, a server could be a CI, and contain a CI for the OS, SQL server, applications. An application CI would contain CIs for application components like DLLs etc.

There are a number of proprietary solutions, but they all cost a fortune. Googling for 'open source configuration management' reveals that there are two meanings, and most people seem to equate 'configuration management' with 'source control system'. But you could have a look on SourceForge to see if there is anyting you can use?

Steve

[small]"Every program can be reduced by one instruction, and every program has at least one bug. Therefore, any program can be reduced to one instruction which doesn't work." (Object::perlDesignPatterns)[/small]
 
Its more information management than confiruation management. Its not a source control systems. Its like being able to get information on server x, seeing how much free memory is has, who owns it, what applications run on it. The user should be allowed to upload this information. It should be tables of data linked to each other in a neat slick and presentable way.
 
I'm a GUI guy and I have to tell you that the DataGrid and the MS Spreadsheet are the most visually UNPleasant controls to include in an app.

If you are creating this app as a webapp then you have a few more options. The simple asp.net repeater control can make things look a little bit better as it is formatted with HTML and has more flexibility.

You will also want to look at simple ways to search for items by their appropriate ids etc. I would tend to focus on these features as it will make the system more managable as it grows.

The Composite Pattern is a good way to put manage data in your app but there are other options too. Take the first day or even 2 to think through your options. This will make your 2 weeks a lot more caffeine free.

What you have been asked to do will require a lot of long days but it can easily be done.
 
Yes, GUI advice is what I really need. Also its going to be a webform application (aspx files).

The mistake I made in previous applications is that I've used datagrids and repeaters but ended up pulling back too much information all at once. While getting the data model is important presenting the information simply and neatly is the key. Perhaps I should google a little on GUI tips for c# applications.
 
Another question. *.ascx files are used to create a control that is used in more than one page. So on every page of the app I want a particular icon and two text controls. Can someone give me an example in c#
 
google Custom Asp .net Controls and you will find it quite easy.

Or look into Server Side includes to automatically include the same html on every page.

If you found that you are polling too much data at once then you will want to look into an architecture that I call "Drilling Down". Give them the basic info (Name). When they click on it, query the information for Model number, Manufacturer. When they click on that again, give them Serial Number, location, and estimated value.

Something like that.
 
Ya - got the ascx controls working. I'll be pulling together environments information. For example. A server X, may have 10 different alias names. What is the disk space on the server. Who owns the server. What blades are on the server. What app servers are on the server. Does it host databases. So you can imagine how the info. will link together. The server might be used for a certain period, say four months. What unix code sets are on the server.

I guess you can ask that question across many servers, web servers, sybase servers, dev environenments...

All the above will link into eachother. The data model will be crucial. I want to develop a tool that is working in two weeks but leaves room for further expansion.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top