I agree with jschell. Here is slightly different version of that: Inventory: id, product_id, count, date Product: id, name, description, price, category_id Category: id, name, description Characteristic: id,name, description Category_Characteristic: category_id, characteristic_id

You should be able to utilize OpenGL library for this project. No need to tell the volunteers you are A++ student to get help. What is good about being an A++ if you cannot write the code for your final year project.

:laugh:

I do like your analogy. We tend to use the Software Design and Software Architecture loosely as equivalent terms. However, there are two different things. In a nutshell, Software Architecture captures nonfunctional requirements( environment and system constraints, technologies, platform,...), analyses high level structure of the software components. The goal is a Software Architecture Design Document which is very important in stakeholders' early decision. In contrast, Software Design or Software Implementation Design to be clear, elicits functional requirements. It is about detail implementation of divers software components. Incidentally, Software Architecture and Software Design don't use the same techniques or methodology to meet their respective goals( they don't have the same goals!!!). The former uses 5 Architectural Views for example produce the Software Architecture Document, but the latter deals with class diagrams, sequence diagrams, use cases, state diagrams, etc... to produce Software code. This is just a glance about a large topic.

Use LinkedList from Java Collection Framework like in the following: // create your class public class MyItem { ....... ........ } //Instantiate your object MyItem item = new MyItem(); List myList = new LinkedList(); myList.add(item);

SCRUM is part of agile process. It deals with small incremental deliveries( 1 or 2 weeks). Actually the SCRUM handles well the change. I worked in team where the SCRUM is the centerpiece. All projects were delivered on time.

That is where a Change Management System comes handy, keeping track of a change request. This is not to say you are totally wrong. Actually, you right when comes to some aspect of team communication, emails are important. However, in a large-scale complex software project with many full-time developers, Test team, Product Manager, Requirement Engineer, Configuration Manager, Project Manager, in short a project that requires a full blown development team you have no choice, but to put implement a good methodology like Agile, among other things. Just emails tracking won't do it.

“The Only Thing That Is Constant Is Change -” By Heraclitu I found his is so true for Software Development. In my Software Engineering training, I took a course titled "Managing Evolving System and Software maintenance". This course demonstrates that most software are not build for change. The best Methodology embraces the change from start and allows iterative development. Agile Software Development is an example that methodology;Rational Unified Process (RUP) is another one. Agile allows incremental delivery of Business value to the project. Therefore, the change is good as it adds clarity to the development. For one reason, in large scale project, the requirement can only became clear in an unspecified time in develoemnt life cycle. The problem is lack of a Change Management System and iterative development process.

You're welcome. Here it is: http://www.hibernate.org/about/annotations

1. Install on your deployment machine -Microsoft web server IIS to store your ASP pages and other application files -Microsoft SQLServer as database server 2.Implement 3-tier Design pattern 3. Have Microsoft Visual Studio or Express Edition of C# or VB on your development machine. 4. Read about ASP.NET, C# or VB.NET, and ADO.NET 5. Ask questions!!!

Great tools. However, with hibernate annotations *.hbm.xml" files aren't need anymore. Check it out.

Hi, If you are using relational database system like MySQL, Oracle, consider using an Object-Relational Mapping framework(ORM) that implements Data Acess Layer(DAL) design pattern . TopLink, Hibernate, ADO.Net, Java JPA, just to name a few, are popular ORM Frameworks. These frameworks abstract DBMS access and handle all database CRUD for you, and do much more. For example using Java JPA, you would save a domain object as follow: EntityManager em; em.persist(BookDTO);// BookDTO is the object to be saved in you database. BookDTO must be annotated as an Entity( @Entity) as far as JPA is concern. You can apply Dependency Injection/IoC to inject the EntityManager in your component. To use DAL patern organize your Domain Model into Business Object(BO) and Data Transfer Object(DTO), and utilize an ORM framework of your choice.

Bakary Konate