"AIRA" Automatic Intelligent Rig Assembler

[Ronron14]

I am an IT Student... As a part of our subject System Analysis and Design, we we're given a Thesis project of developing an Application and our approved proposal is called AIRA or Automatic Intelligent Rig Assembler... AIRA is a Web App that will help a user build his/her own PC with just entering his/her Budget.... I'm still forming up algorithms... My question is... When building your PC.. How much percent of the given budget are you going to spend for each PC Components...

Something like this:

CPU: 20%

GFX: 25%

MOBO: 10

RAM: 15%

HDD: 10%

Chassis: 10%

CPU Cooler: 5%

Chassis Fans: 5% 

 

[Interfectorem]

 

I am an IT Student... As a part of our subject System Analysis and Design, we we're given a Thesis project of developing an Application and our approved proposal is called AIRA or Automatic Intelligent Rig Assembler... AIRA is a Web App that will help a user build his/her own PC with just entering his/her Budget.... I'm still forming up algorithms... My question is... When building your PC.. How much percent of the given budget are you going to spend for each PC Components...

Something like this:

CPU: 20%

GFX: 25%

MOBO: 10

RAM: 15%

HDD: 10%

Chassis: 10%

CPU Cooler: 5%

Chassis Fans: 5% 

 

Well it really depends on what the computer is going to be used for. But those percentages look well balanced. Although you could maybe discard the chassis fans percantage and add that to the CPU, since most chassis come with fans. But it looks balanced.

 

Best of luck with your project, seems very exciting.

[Shroomster]

Propably more for gfx as it is the most important bit in a pc. Like 30-35%

[Shroomster]

Damn ninja.

[ShadowCaptain]

My GPU was like 50%

[TheRunningOtaku]

I think it depends on the use... Above a certain amount the going from an i5 to i7 won't do you much, and the same with going from $150 of RAM to $300 of RAM...

The algorithm would have to change in price brackets, with more being put to the GPU at higher prices.

An option for the user to enter the use case (e.g. video editing, gaming, home theatre PC, etc) would also help as if you're doing a server, you won't need K skew chips and all that.

[DigitalHermit]

Sounds great, but I think it would better to add a context to choose from, making the cost divisions more flexible (i.e. video rendering will put higher priority on CPU, gaming will put higher priority on GPU, etc.)...

[APrettyCoolWalrus]

That seems really cool!

[Shroomster]

My GPU was like 50%

Mine was even higher. LOL

[Ronron14]

Sorry.. I forgot to include that the User will select a Build Category... Gaming Build, Casual Build and Workstation Build.. Should I disregard the Chassis Cooler...? Btw thanks for the fast response people..!  Probably for the Gaming Build higher percentage for the GFX...? And higher CPU for the Workstation Build....?

[DigitalHermit]

Sorry.. I forgot to include that the User will select a Build Category... Gaming Build, Casual Build and Workstation Build.. Should I disregard the Chassis Cooler...? Btw thanks for the fast response people..!  Probably for the Gaming Build higher percentage for the GFX...? And higher CPU for the Workstation Build....?

 

That's a good direction to take...

I'd suggest something more advanced such as checkboxes which cover what the user plans to do with the system...

[Ronron14]

Can anyone please help me... I'm perfecting my Database... Anyone knows how to design ERDs...? So I have a Table for Case Fans named tb_Chssis_Fan and under that table I is an Attribute called size... And when it comes to size it is for sure to have repeating values and the goal in designing an ERD is eliminating repeating values... So should I create a table for Case Fan Sizes...? Or it is okay for the Size Attributes to have no Primary Table at all for it is a Continuous Variable or simply a Number...?

[pbenologa]

Mine was even higher. LOL

I call BS. 

[Shroomster]

I call BS.

Gtx TITAN nearly at launch. And it cost here 999€ which is ~1250$

[DigitalHermit]

Can anyone please help me... I'm perfecting my Database... Anyone knows how to design ERDs...? So I have a Table for Case Fans named tb_Chssis_Fan and under that table I is an Attribute called size... And when it comes to size it is for sure to have repeating values and the goal in designing an ERD is eliminating repeating values... So should I create a table for Case Fan Sizes...? Or it is okay for the Size Attributes to have no Primary Table at all for it is a Continuous Variable or simply a Number...?

 

This is where it gets complicated... (also what are ERDs???)

 

If it's a database fans, the field for size should have repeating fixed values (80,92,120,140,etc) since it can be said that it is a category...

Fields for Airflow/Static Pressure, Ariflow Rate (how many CFM), and Control (PWM or otherwise), and cost...

 

I'd suggest that the algo for choosing a fan be dependent on the chosen case and mobo (for fan control)... i.e. it would suggest at least 1 SP fan for rear exhaust and the rest are AF fans... with the fans at the lowest priority when it comes to selecting the parts... basically, the program would try to exhaust the budget on everything internal, then the case, before the fans...