Southperry.net
Identifying Quality Attributes - Printable Version

+- Southperry.net (https://www.southperry.net)
+-- Forum: Social (https://www.southperry.net/forumdisplay.php?fid=14)
+--- Forum: Rubik's Cube (https://www.southperry.net/forumdisplay.php?fid=58)
+--- Thread: Identifying Quality Attributes (/showthread.php?tid=11633)



Identifying Quality Attributes - Conciente - 2009-05-24

----------------


Identifying Quality Attributes - holyforest - 2009-05-24

Well, for performance it's really quite simple. You need to guarantee that this system won't go haywire and shut down in the middle of average work day.


Identifying Quality Attributes - Fiel - 2009-05-25

holyforest Wrote:Well, for performance it's really quite simple. You need to guarantee that this system won't go haywire and shut down in the middle of average work day.

That's stability, not performance.

You also want encryption on the network - don't want people to break into the files.


Identifying Quality Attributes - KajitiSouls - 2009-05-25

Fiel Wrote:That's stability, not performance.

You also want encryption on the network - don't want people to break into the files.

HIPAA laws, oyas xD You should probably add that such files should NOT be accessed by any working personnel who have no business with a specific patient, including physicians.

I've come to think about banking situations when you mention this assignment. Say there's a joint bank account owned by a father and a mother, and it has 500 dollars in it. At 1:00.00 pm, the mother makes a withdrawal worth 267 dollars to pay up front for some pharmaceutical medicine. Also at 1:00.00 pm, the father makes a withdrawal worth 400 dollars to invest in a startup company he believes will revolutionize the next generation of technology. This clearly can't happen and is illegal. There has to be a way to prevent accidents such as these from occurring.

For modifiability, this sorta goes hand in hand with data integrity, but there should be encapsulation of specific data, and there should only be ready methods designed in mind for the system's purpose. In this case, it should be fairly easy and convenient to add items to a patient's bill, but it should be very hard to remove an item (an administrator/manager level thing).

I dunno if this will go under any of the categories, but with each patient, there should be a unique ID number of some sort, since there could be conceivably over a hundred people named "John Smith" within a large city alone. I've done signature validation work with the WA Secretary of State, and they had a database with every registered voter's name and stuff. Doing a search on common names like those will turn up at least 400 people xD An SSN usually does the trick, as it is universal to the country that issued it and other pharmacies can recognize it immediately.


Identifying Quality Attributes - Stereo - 2009-05-28

KajitiSouls Wrote:I've come to think about banking situations when you mention this assignment. Say there's a joint bank account owned by a father and a mother, and it has 500 dollars in it. At 1:00.00 pm, the mother makes a withdrawal worth 267 dollars to pay up front for some pharmaceutical medicine. Also at 1:00.00 pm, the father makes a withdrawal worth 400 dollars to invest in a startup company he believes will revolutionize the next generation of technology. This clearly can't happen and is illegal. There has to be a way to prevent accidents such as these from occurring.

As long as it's limited to a single "open" transaction that wouldn't be a problem. Even if they both request a transaction, it should only accept 1 if they occur simultaneously.


Identifying Quality Attributes - Fiel - 2009-05-28

Stereo Wrote:As long as it's limited to a single "open" transaction that wouldn't be a problem. Even if they both request a transaction, it should only accept 1 if they occur simultaneously.

For any server or database, linearity is a no-no. Multithreading and parallelism is the way to go.


Identifying Quality Attributes - KajitiSouls - 2009-05-28

Fiel Wrote:For any server or database, linearity is a no-no. Multithreading and parallelism is the way to go.

Chinchilla man strikes again!

Seriously Stereo, you want linear channels in a pharmacy of unspecified size? Are you crazy!?