My experience with networking, and .NET to be blogged here. Since I dont have an always online connection at home, the posts may not be live enough and perhaps even sporadic.
Thanks. I've fixed it now. The thing is that the Outlook Web Access that we use to check our @lums.edu.pk emails is an https:// url. I've got used to typing that so much that half of the time when I should be typing http://, I type https://. That was the case here with the href attribute.
Just one comment : It dint have any logical architectural specification of the proposed solution ? I have seen such artifacts always containing arcthitectural diagrams .
Thanks Hammad. The way we were told and the templates we were given was that it should be a requirements document for the customer evaluation. The logical architecture is yet to come in functional specification. Do feel free to comment on your agreement or otherwise on this scheme of things. Talking of customer requirements, I myself wasnt comfortable with the mention of terms like "database" and "customer validation" since these are mainly computer artifacts, and I would like to see a requirements document based on non computer terms. I dont know how correct that feeling is, though.
4 comments:
The download link is not working.
Thanks. I've fixed it now. The thing is that the Outlook Web Access that we use to check our @lums.edu.pk emails is an https:// url. I've got used to typing that so much that half of the time when I should be typing http://, I type https://. That was the case here with the href attribute.
looks good for sure.
Just one comment : It dint have any logical architectural specification of the proposed solution ? I have seen such artifacts always containing arcthitectural diagrams .
Thanks Hammad. The way we were told and the templates we were given was that it should be a requirements document for the customer evaluation. The logical architecture is yet to come in functional specification. Do feel free to comment on your agreement or otherwise on this scheme of things. Talking of customer requirements, I myself wasnt comfortable with the mention of terms like "database" and "customer validation" since these are mainly computer artifacts, and I would like to see a requirements document based on non computer terms. I dont know how correct that feeling is, though.
Post a Comment